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

feat: include some settings as fields in the lockfile #6557

Merged
merged 3 commits into from May 20, 2023
Merged

Conversation

zkochan
Copy link
Member

@zkochan zkochan commented May 17, 2023

ref #6312

Some settings influence the structure of the lockfile, so we cannot reuse the lockfile if those settings change. As a result, we need to store such settings in the lockfile. This way we will know with which settings the lockfile has been created.

@zkochan zkochan marked this pull request as ready for review May 20, 2023 13:45
@zkochan zkochan requested a review from a team May 20, 2023 13:45
@zkochan zkochan merged commit 9c4ae87 into main May 20, 2023
13 of 14 checks passed
@zkochan zkochan deleted the fix/6312 branch May 20, 2023 23:40
zkochan added a commit that referenced this pull request May 30, 2023
chris-olszewski added a commit to vercel/turbo that referenced this pull request Jun 5, 2023
### Description

Adds parse support for the new lockfile version added in
pnpm/pnpm#6557 fixing #5117

The behavioral change is pretty small for us. The new information was
added to allow for `pnpm install --frozen-lockfile` to produce an
identical lockfile even if the `.npmrc` that was present during the
lockfile's creation is no longer present. This does lead to a better UX
for prune users as they will no longer need to copy `.npmrc` in their
`Dockerfile`.

### Testing Instructions

Existing unit tests pass and added new fixture with the settings field
that correctly parses.

---------

Co-authored-by: Chris Olszewski <Chris Olszewski>
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

2 participants