* fix: check for both bundleDependencies and bundledDependencies (#7411)
update to code that didn't correctly check both bundleDependencies and bundledDependencies
* fix: support boolean value for bundleDependencies (#7411)
fix so that a 'true' value in the bundleDependencies field is correctly interpreted
(as meaning all dependencies are bundled)
close #7411
* fix: allow saving of boolean bundledDependencies values
updates prior fix to allow saving booleans to bundledDependencies field.
* fix: add test coverage for bundledDependencies fixes (#7411)
add local tarball test and bundledDependencies=true test
update existing tests to confirm that bundled dependencies aren't installed
* fix: update registry-mock
* docs: update changeset
* fix: update bundleDependencies tests
* Revert "fix: update registry-mock"
This reverts commit 0c4b7ede21.
* Revert "Revert "fix: update registry-mock""
This reverts commit 9828dfce91.
* test: update integrities in test lockfiles
* test: retry twice
* test: move bundle deps test to separate file
---------
Co-authored-by: Zoltan Kochan <z@kochan.io>
A new setting added for symlinking [injected dependencies](https://pnpm.io/package_json#dependenciesmetainjected) from the workspace, if their dependencies use the same peer dependencies as the dependent package. The setting is called `dedupe-injected-deps`
* fix: avoid empty cloned files in Windows
* chore: add changesets
* chore: update changesets
* fix: remove duplicate dependency
* fix: try to set workers number to 1 in Windows
* revert: 1 worker in Windows tests
* fix: throw error when current drive does not support CoW
(IMPORTANT) When the package tarballs aren't hosted on the same domain on which the registry (the server with the package metadata) is, the dependency keys in the lockfile should only contain `/<pkg_name>@<pkg_version`, not `<domain>/<pkg_name>@<pkg_version>`.
This change is a fix to avoid the same package from being added to `node_modules/.pnpm` multiple times. The change to the lockfile is backward compatible, so previous versions of pnpm will work with the fixed lockfile.
We recommend that all team members update pnpm in order to avoid repeated changes in the lockfile.
* feat: default network-concurrency to cpu count
It was found that setting network-concurrency to the exact number of
CPU cores gives fastest installation
* perf: set 16 as min default concurrency
* docs: add comment
---------
Co-authored-by: Zoltan Kochan <z@kochan.io>
