You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session. Dismiss alert
Security News pnpm 9.5 Introduces Catalogs: Shareable Dependency Version Specifiers pnpm 9.5 introduces a Catalogs feature, enabling shareable dependency version specifiers, reducing merge conflicts and improving support for monorepos. pnpm is eight years into its unique approach to package management, and continues to gain traction, especially among those who need efficiency and support for monor
Minor Changes New setting called virtual-store-dir-max-length added to modify the maximum allowed length of the directories inside node_modules/.pnpm. The default length is set to 120 characters. This setting is particularly useful on Windows, where there is a limit to the maximum length of a file path #7355. Patch Changes A dependency is hoisted to resolve an optional peer dependency only if it s
Major Changes Node.js v16 and 17 support discontinued If you still require Node.js 16 or 17, don't worry. We ship pnpm bundled with Node.js. This means that regardless of which Node.js version you've installed, pnpm will operate using the necessary Node.js runtime. For this to work you need to install pnpm either using the standalone script or install the @pnpm/exe package. Corepack compatiblity:
For installation instructions see: https://pnpm.io/9.x/installation Major Changes Node.js v16 support dropped. Use at least Node.js v18.12. Lockfile version bumped to v7. Support for lockfile v5 is dropped. Use pnpm v8 to convert lockfile v5 to lockfile v6 #7470. The dedupe-injected-deps setting is true by default. The default value of the link-workspace-packages setting changed from true to false
Minor Changes Improve performance of installation by using a worker pool for extracting packages and writing them to the content-addressable store #6850 The default value of the resolution-mode setting is changed to highest. This setting was changed to lowest-direct in 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 (reso
We are excited to announce the latest release of pnpm! To install it, check the installation page. Major Changes Node.js 14 Support Discontinued If you still require Node.js 14, don't worry. We ship pnpm bundled with Node.js. This means that regardless of which Node.js version you've installed, pnpm will operate using the necessary Node.js runtime. For this to work you need to install pnpm either
Major Changes Node.js 14 support discontinued If you still require Node.js 14, don't worry. We ship pnpm bundled with Node.js. This means that regardless of which Node.js version you've installed, pnpm will operate using the necessary Node.js runtime. For this to work you need to install pnpm either using the standalone script or install the @pnpm/exe package. Configuration updates: auto-install-p
Major Changes auto-install-peers is true by default. The registry field is removed from the resolution object in pnpm-lock.yaml. save-workspace-protocol is rolling by default. When there's a files field in the package.json, only deploy those files that are listed in it. Use the same logic also when injecting packages. This behavior can be changed by setting the deploy-all-files setting to true #59
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く