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

lockfile/6.0.md and dependency-paths #5

Open
CraigMacomber opened this issue Mar 11, 2024 · 0 comments
Open

lockfile/6.0.md and dependency-paths #5

CraigMacomber opened this issue Mar 11, 2024 · 0 comments

Comments

@CraigMacomber
Copy link

I was reading https://github.com/pnpm/spec/blob/master/lockfile/6.0.md and noticed some things:

### lockfileVersion

A [ComVer](https://github.com/staltz/comver) starting with the major number `4`.

### packages

This is a mapping of dependency path to dependency object. The [dependency path](../dependency-path.md) is relative (e.g., `/[email protected]`) if the dependency
is from the registry specified in the registry property, or absolute (e.g., `registry.node-modules.io/[email protected]`) if the package's
registry differs from the one specified as default in the shrinkwrap file.
That should say 6 right?

I think the major version is 6 now, not 4.

Also dependency-path.md describes a format that seems like the one use in v5 lock files, not the one used in v6 lock files. There was a change to the format between v5 and v6 (I see /mime/1.6.0 change to /[email protected] and /webpack-cli/4.10.0_fzn43tb6bdtdxy2s3aqevve2su replaced with /[email protected]([email protected])([email protected])([email protected]) when updating for example). This change does not seem to be documented anywhere that I can find.

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

No branches or pull requests

1 participant