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

fix(lockfile): only consider package.json beside lockfile in workspace property #22179

Merged

Conversation

dsherret
Copy link
Member

Closes #22176 (see detail there)

.skip_output_check();
// the lockfile should stay the same as the above because the package.json
// was found in a different directory
lockfile.assert_matches_json(expected_lockfile.clone());
Copy link
Member Author

Choose a reason for hiding this comment

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

Previously this would flip flop back and forth between the packages from package.json and packages-a/package.json. Now it just stays being the ones in package.json. In the future, we should get deno to understand npm workspaces beyond just for byonm and then it could include all the members in the lockfile (luckily the lockfile code already has support for this... it's just getting it into the CLI sometime).

@dsherret dsherret merged commit 0e1cae3 into denoland:main Jan 30, 2024
14 checks passed
@dsherret dsherret deleted the fix_lockfile_package_json_subfolder branch January 30, 2024 14:26
littledivy pushed a commit that referenced this pull request Feb 1, 2024
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.

Lockfile workspace property behaves poorly in a npm workspace
2 participants