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

FUTURE: enable BYONM by default #23194

Merged
merged 4 commits into from
Apr 2, 2024

Conversation

bartlomieju
Copy link
Member

@bartlomieju bartlomieju commented Apr 2, 2024

When DENO_FUTURE=1 env var is present, then BYONM
("bring your own node_modules") is enabled by default.
That means that is there's a package.json present, users
are expected to explicitly install dependencies from that file.

Towards #23151

cli/args/mod.rs Outdated Show resolved Hide resolved
Copy link
Member

@dsherret dsherret left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@bartlomieju bartlomieju merged commit c0b7454 into denoland:main Apr 2, 2024
17 checks passed
@bartlomieju bartlomieju deleted the deno_future_byonm branch April 2, 2024 22:43
satyarohith pushed a commit that referenced this pull request Apr 11, 2024
When `DENO_FUTURE=1` env var is present, then BYONM
("bring your own node_modules") is enabled by default.
That means that is there's a `package.json` present, users
are expected to explicitly install dependencies from that file.

Towards #23151
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants