Update dependency @pnpm/types to ^8.10.0 #19
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![mend-5034428[bot]](https://avatars.githubusercontent.com/u/5034428?s=60&v=4){kind=small}
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
^8.4.0->^8.10.0Release Notes
pnpm/pnpm (@pnpm/types)
v8.10.0Compare Source
Minor Changes
Support for multiple architectures when installing dependencies #5965.
You can now specify architectures for which you'd like to install optional dependencies, even if they don't match the architecture of the system running the install. Use the
supportedArchitecturesfield inpackage.jsonto define your preferences.For example, the following configuration tells pnpm to install optional dependencies for Windows x64:
{ "pnpm": { "supportedArchitectures": { "os": ["win32"], "cpu": ["x64"] } } }Whereas this configuration will have pnpm install optional dependencies for Windows, macOS, and the architecture of the system currently running the install. It includes artifacts for both x64 and arm64 CPUs:
{ "pnpm": { "supportedArchitectures": { "os": ["win32", "darwin", "current"], "cpu": ["x64", "arm64"] } } }Additionally,
supportedArchitecturesalso supports specifying thelibcof the system.The
pnpm licenses listcommand now accepts the--filteroption to check the licenses of the dependencies of a subset of workspace projects #5806.Patch Changes
Allow scoped name as bin name #7112.
When running scripts recursively inside a workspace, the logs of the scripts are grouped together in some CI tools. (Only works with
--workspace-concurrency 1)Print a warning when installing a dependency from a non-existent directory #7159
Should fetch dependency from tarball url when patching dependency installed from git #7196
pnpm setupshould add a newline at the end of the updated shell config file #7227.Improved the performance of linking bins of hoisted dependencies to
node_modules/.pnpm/node_modules/.bin#7212.Wrongful ELIFECYCLE error on program termination #7164.
pnpm publishshould not pack the same file twice sometimes #6997.The fix was to update
npm-packlistto the latest version.Our Gold Sponsors
Our Silver Sponsors
v8.9.0Compare Source
Minor Changes
🚀Performance improvement: Use reflinks instead of hard links by default on macOS and Windows Dev Drives #5001.
The list of packages that are allowed to run installation scripts now may be provided in a separate configuration file. The path to the file should be specified via the
pnpm.onlyBuiltDependenciesFilefield inpackage.json. For instance:{ "dependencies": { "@​my-org/policy": "1.0.0" } "pnpm": { "onlyBuiltDependenciesFile": "node_modules/@​my-org/policy/allow-build.json" } }In the example above, the list is loaded from a dependency. The JSON file with the list should contain an array of package names. For instance:
With the above list, only
esbuildand@reflink/reflinkwill be allowed to run scripts during installation.Related issue: #7137.
Add
disallow-workspace-cyclesoption to error instead of warn about cyclic dependenciesAllow
env rmto remove multiple node versions at once, and introduceenv addfor installing node versions without setting as default #7155.Patch Changes
pnpm whywhen the dependencies tree is too big, the command will now prune the tree to just 10 end leafs and now supports--depthargument #7122.neverBuiltDependenciesandonlyBuiltDependenciesfrom the rootpackage.jsonof the workspace, whenshared-workspace-lockfileis set tofalse#7141.pnpm.overridesreplacingresolutions, the two are now merged. This is intended to make it easier to migrate from Yarn by allowing one to keep usingresolutionsfor Yarn, but adding additional changes just for pnpm usingpnpm.overrides.Our Gold Sponsors
Our Silver Sponsors
v8.8.0Compare Source
Minor Changes
--reporter-hide-prefixoption forruncommand to hide project name as prefix for lifecycle log outputs of running scripts #7061.Patch Changes
--ignore-scriptscommand to install, when runningpnpm dedupe --ignore-scripts#7102.node-linkeris set tohoisted, thepackage.jsonfiles of the existing dependencies insidenode_moduleswill be checked to verify their actual versions. The data in thenode_modules/.modules.yamlandnode_modules/.pnpm/lock.yamlmay not be fully reliable, as an installation may fail after changes to dependencies were made but before those state files were updated #7107.Our Gold Sponsors
Our Silver Sponsors
v8.7.0Compare Source
Minor Changes
resolution-modesetting is changed tohighest. This setting was changed tolowest-directin v8.0.0 and some users were not happy with the change. A twitter poll concluded that most of the users want the old behaviour (resolution-modeset tohighestby default). This is a semi-breaking change but should not affect users that commit their lockfile #6463.Patch Changes
peerDependencies#615.pnpm import#6233.peerDependenciesinpnpm.overrides#6759.pnpm patchshould write patch files with a trailing newline #6905.Our Gold Sponsors
Our Silver Sponsors
v8.6.0Compare Source
Minor Changes
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.
A new field will now be present in the lockfile:
settings. It will store the values of two settings:autoInstallPeersandexcludeLinksFromLockfile. If someone tries to perform afrozen-lockfileinstallation and their active settings don't match the ones in the lockfile, then an error message will be thrown.The lockfile format version is bumped from v6.0 to v6.1.
Related PR: #6557
Related issue: #6312
A new setting,
exclude-links-from-lockfile, is now supported. When enabled, specifiers of local linked dependencies won't be duplicated in the lockfile.This setting was primarily added for use by Bit CLI, which links core aspects to
node_modulesfrom external directories. As such, the locations may vary across different machines, resulting in the generation of lockfiles with differing locations.Patch Changes
npm:foo@1.0.0becomesnpm:foo@1.1.0.workspace:protocol is not found in the workspace #4477.pnpm rebuildshould not fail whennode-linkeris set tohoistedand there are skipped optional dependencies #6553.Our Gold Sponsors
Our Silver Sponsors
v8.5.0Compare Source
Minor Changes
pnpm patch-removecommand added #6521.Patch Changes
pnpm link -g <pkg-name>should not modify thepackage.jsonfile #4341.node_modulesdirectory #6510.enginesfield should match prerelease versions #6509.Our Gold Sponsors
Our Silver Sponsors
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.