This repository has been archived by the owner on Apr 14, 2023. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
7.0.0
->7.11.0
7.9.5
->7.11.0
Release Notes
pnpm/pnpm
v7.11.0
Compare Source
Minor Changes
pnpm patch
: edit the patched package in a directory specified by the--edit-dir
option. E.g.,pnpm patch express@3.1.0 --edit-dir=/home/xxx/src/patched-express
#5304Patch Changes
Our Gold Sponsors
Our Silver Sponsors
What's Changed
New Contributors
Full Changelog: pnpm/pnpm@v7.10.0...v7.11.0
v7.10.0
Compare Source
Minor Changes
New time-based resolution strategy supported.
When
resolution-mode
is set totime-based
, pnpm will resolve dependencies the following way:foo@^1.1.0
in the dependencies, then1.1.0
will be installed.With this resolution mode installations with hot cache are faster. It also reduces the chance of subdependency hijacking as subdependencies will be updated only if direct dependencies are updated.
This resolution mode works only with npm's full metadata. So it is slower in some scenarios. However, if you use Verdaccio v5.15.1 or newer, you may set the
registry-supports-time-field
setting totrue
, and it will be really fast.Related RFC.
Enhance
pnpm env
with theremove
command. To remove a Node.js version installed by pnpm, run:Patch Changes
pnpm store prune
should remove all cached metadata.Our Gold Sponsors
Our Silver Sponsors
What's Changed
New Contributors
Full Changelog: pnpm/pnpm@v7.9.5...v7.10.0
v7.9.5
Compare Source
Patch Changes
NODE_PATH
whenprefer-symlinked-executables
is enabled #5251.node_modules
, even if the target directory doesn't exist #5219.Our Gold Sponsors
Our Silver Sponsors
What's Changed
New Contributors
Full Changelog: pnpm/pnpm@v7.9.4...v7.9.5
v7.9.4
Compare Source
Patch Changes
pnpm env
: for Node.js<16 install the x64 build on Darwin ARM as ARM build is not available #5239.pnpm env
: log a message when the node.js tarball starts the download #5241.pnpm install --merge-git-branch-lockfile
when the lockfile is up to date #5212.Our Gold Sponsors
Our Silver Sponsors
What's Changed
New Contributors
Full Changelog: pnpm/pnpm@v7.9.3...v7.9.4
v7.9.3
Compare Source
Patch Changes
Our Gold Sponsors
Our Silver Sponsors
What's Changed
Full Changelog: pnpm/pnpm@v7.9.2...v7.9.3
v7.9.2
Compare Source
Patch Changes
Our Gold Sponsors
Our Silver Sponsors
v7.9.1
Compare Source
Patch Changes
pnpm setup
: don't usesetx
to set env variables on Windows.Our Gold Sponsors
Our Silver Sponsors
v7.9.0
Compare Source
Minor Changes
ignore-dep-scripts
istrue
, ignore scripts of dependencies but run the scripts of the project.ignore-compatibility-db
is set totrue
, the compatibility database will not be used to patch dependencies #5132.Patch Changes
pnpm setup
should suggest users to source the config instead of restarting the terminal.bin
that points to an.exe
file on Windows #5159.verify-store-integrity
is set tofalse
.Our Gold Sponsors
Our Silver Sponsors
v7.8.0
Compare Source
Minor Changes
publishConfig.directory
is set, only symlink it to other workspace projects ifpublishConfig.linkDirectory
is set totrue
. Otherwise, only use it for publishing #5115.Patch Changes
Our Gold Sponsors
Our Silver Sponsors
What's Changed
New Contributors
Full Changelog: pnpm/pnpm@v7.7.1...v7.8.0
v7.7.1
Compare Source
Patch Changes
auto-install-peers
is set totrue
and the peer dependency is indevDependencies
oroptionalDependencies
#5080.workspace:^
orworkspace:~
version specs are used in a workspace.Our Gold Sponsors
Our Silver Sponsors
What's Changed
auto-install-peers=true
by @zkochhttps://github.com/pnpm/pnpm/pull/5120l/5120Full Changelog: pnpm/pnpm@v7.7.0...v7.7.1
v7.7.0
Compare Source
Minor Changes
Add experimental lockfile format that should merge conflict less in the
importers
section. Enabled by setting theuse-inline-specifiers-lockfile-format = true
feature flag in.npmrc
.If this feature flag is committed to a repo, we recommend setting the minimum allowed version of pnpm to this release in the
package.json
engines
field. Once this is set, older pnpm versions will throw on invalid lockfile versions.Add
publishDirectory
field to the lockfile and relink the project when it changes.verify-store-integrity=false
makes pnpm skip checking the integrities of files in the global content-addressable store.Allow to set
only-built-dependencies[]
through.npmrc
.Patch Changes
publishConfig.directory
) #3901.pnpm deploy
should inject local dependencies of all types (dependencies, optionalDependencies, devDependencies) #5078.publishConfig.directory
set, dependent projects should install the project from that directory #3901.zshrc
in the right directory when a$ZDOTDIR
is set.Our Gold Sponsors
Our Silver Sponsors
What's Changed
New Contributors
Full Changelog: pnpm/pnpm@v7.6.0...v7.7.0
v7.6.0
Compare Source
Minor Changes
A new setting supported:
prefer-symlinked-executables
. Whentrue
, pnpm will create symlinks to executables innode_modules/.bin
instead of command shims (but on POSIX systems only).This setting is
true
by default whennode-linker
is set tohoisted
.Related issue: #4782.
When
lockfile-include-tarball-url
is set totrue
, every entry inpnpm-lock.yaml
will contain the full URL to the package's tarball #5054.Patch Changes
pnpm deploy
should include all dependencies by default #5035.Don't print warnings about file verifications. Just print info messages instead.
pnpm publish --help
should print the--recursive
and--filter
options #5019.It should be possible to run exec/run/dlx with the
--use-node-version
option.pnpm deploy
should not modify the lockfile #5071pnpm deploy
should not fail in CI #5071When
auto-install-peers
is set totrue
, automatically install direct peer dependencies #5028.So if your project the next manifest:
pnpm will install both lodash and react as a regular dependencies.
Our Gold Sponsors
Our Silver Sponsors
What's Changed
lockfile-include-tarball-url
option by @MBelnihttps://github.com/pnpm/pnpm/pull/5054l/5054New Contributors
Full Changelog: pnpm/pnpm@v7.5.2...v7.6.0
v7.5.2
Compare Source
Patch Changes
Our Gold Sponsors
Our Silver Sponsors
What's Changed
Full Changelog: pnpm/pnpm@v7.5.1...v7.5.2
v7.5.1
Compare Source
Patch Changes
node_modules
#4988.Our Gold Sponsors
Our Silver Sponsors
What's Changed
New Contributors
Full Changelog: pnpm/pnpm@v7.5.0...v7.5.1
v7.5.0
Compare Source
Minor Changes
A new value
rolling
for optionsave-workspace-protocol
. When selected, pnpm will save workspace versions using a rolling alias (e.g."foo": "workspace:^"
) instead of pinning the current version number (e.g."foo": "workspace:^1.0.0"
). Usage example, in the root of your workspace, create a.npmrc
with the following content:Patch Changes
pnpm remove <pkg>
should not fail in a workspace that has patches #4954pnpm env use
should throw an error on a system that use the MUSL libc.Our Gold Sponsors
Our Silver Sponsors
What's Changed
Full Changelog: pnpm/pnpm@v7.4.1...v7.5.0
v7.4.1
Compare Source
Patch Changes
pnpm install
in a workspace with patches should not fail when doing partial installation #4954.--lockfile-only
is used. Even iffrozen-lockfile
istrue
#4951.patchedDependencies
field topnpm-lock.yaml
.Our Gold Sponsors
Our Silver Sponsors