workspaces: Lockfile should be placed next to the workspace config file #24161
Labels
feat
new feature (which has been agreed to/accepted)
Comments
12 tasks
zebreus
pushed a commit
to zebreus/deno
that referenced
this issue
Jul 8, 2024
Adds much better support for the unstable Deno workspaces as well as support for npm workspaces. npm workspaces is still lacking in that we only install packages into the root node_modules folder. We'll make it smarter over time in order for it to figure out when to add node_modules folders within packages. This includes a breaking change in config file resolution where we stop searching for config files on the first found package.json unless it's in a workspace. For the previous behaviour, the root deno.json needs to be updated to be a workspace by adding `"workspace": ["./path-to-pkg-json-folder-goes-here"]`. See details in denoland/deno_config#66 Closes denoland#24340 Closes denoland#24159 Closes denoland#24161 Closes denoland#22020 Closes denoland#18546 Closes denoland#16106 Closes denoland#24160
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When in a workspace setting the
deno.lockfile needs to be created next to thedeno.json(c)file that has theworkspacekey.Additionally multiple lock files in a workspace should not be allowed and cause a hard error as it might lead to surprising results if they are being silently ignored.
The text was updated successfully, but these errors were encountered: