lockfile/6.0.md and dependency-paths
Opened this issue · 0 comments
CraigMacomber commented
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., `/foo@1.0.0`) if the dependency
is from the registry specified in the registry property, or absolute (e.g., `registry.node-modules.io/foo@1.0.0`) 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 /mime@1.6.0
and /webpack-cli/4.10.0_fzn43tb6bdtdxy2s3aqevve2su
replaced with /webpack-cli@4.10.0(webpack-bundle-analyzer@4.10.1)(webpack-dev-server@4.6.0)(webpack@5.89.0)
when updating for example). This change does not seem to be documented anywhere that I can find.