Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Denying env permission for LUME_LOGS and LUME_NOCACHE should not be fatal #551

Closed
teleclimber opened this issue Jan 11, 2024 · 3 comments
Closed
Labels
bug Something isn't working

Comments

@teleclimber
Copy link

Version

2.02

Platform

Mac OS / all

What steps will reproduce the bug?

Build a lume site without allowing env permissions in Deno.

How often does it reproduce? Is there a required condition?

Always, so long as you deny access to these ENV vars.

What is the expected behavior?

Default values should be used for these variables instead of exiting.

What do you see instead?

script exits.

Additional information

No response

@teleclimber teleclimber added the bug Something isn't working label Jan 11, 2024
oscarotero added a commit that referenced this issue Jan 11, 2024
@oscarotero
Copy link
Member

That's fair.
I just made some changes. Can you test if it works fine to you before releasing?
You have to upgrade to the latest dev version of Lume with deno task lume upgrade --dev.

@oscarotero
Copy link
Member

fix released in v2.0.3

@teleclimber
Copy link
Author

Yes that's much better thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants