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: don't include the version for local directory dependencies #6695

Merged
merged 4 commits into from
Jun 21, 2023

Conversation

zkochan
Copy link
Member

@zkochan zkochan commented Jun 21, 2023

There is no need to include the version of a dependency in the lockfile,

if that dependency is installed from a local directory

There is no need to include the version of a dependency in the lockfile,

if that dependency is installed from a local directory
@zkochan zkochan requested a review from a team June 21, 2023 16:19
@jakebailey
Copy link
Member

Do things still work if a workspace has multiple versions of the same package in the same workspace and needs to resolve them separately, like on DT?

My impression was that the lockfile contents are used for resolution and so the version may matter.

@zkochan
Copy link
Member Author

zkochan commented Jun 21, 2023

It should work because the file location is used as the pkg id. The version is redundant information that isn't used.

@zkochan zkochan merged commit 61f22f9 into main Jun 21, 2023
13 of 14 checks passed
@zkochan zkochan deleted the no-version-for-local-dep branch June 21, 2023 17:04
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.

None yet

4 participants