* chore: manifest-utils to jest
* chore: matcher to jest
* chore: modules-yaml to jest
* chore: npm-registry-agent to jest
Replaced `proxyquire` with jest mocking
Fixed `OPTS.strictSSL` fixture to be a boolean as that's what the
agent's option type expects.
`npm-registry-agent` self-links as a devDependency for importing
PR #2913
ref #2858
As of pnpm v3, pnpm fails if the configs that were used when creating node_modules differ from the present ones. For instance, if independent-leaves is set to false globally but installation was done using pnpm install --independent-leaves. Running pnpm add foo will fail. Only pnpm add foo --independent-leaves will work
These changes are making this less strict. If node_modues was created using some configs, installation will only fail if the present configs are set locally (or via CLI flags) and they have incompatible values.
So if pnpm install --independent-leaves was used, then pnpm add foo will work. But pnpm add foo --no-independent-leaves will fail.
PR #2034
New config added that allows hoisting packages by pattern.
This substitutes the shamefully-flatten config that hoist all
dependencies and makes them available for application code.
The new config gives access to the hoisted packages only to
dependencies inside node_modules.
close#1998close#1938
PR #1997
This changes the way node_modules information of importers is
stored. The initial implementation in #1373 used a separate
`.modules.yaml` in every importer's node_modules directory.
Keeping only one `.modules.yaml` makes it easier to get all the
necessary info during recursive installation.
ref #1366
