Changelog
1.12.3
Important: This release contains a cache bump. It will cause the very first install following the upgrade to take slightly more time, especially if you don't use the Offline Mirror feature. After that everything will be back to normal.
Fixes an issue with yarn audit
when using workspaces
Uses NODE_OPTIONS
to instruct Node to load the PnP hook, instead of raw CLI arguments
Caveat: This change might cause issues for PnP users having a space inside their cwd (cf nodejs/node#24065)
Fixes Gulp when used with Plug'n'Play
Fixes an issue with yarn audit
when the root package was missing a name
Fixes an issue with yarn audit
when a package was depending on an empty range
Fixes an issue with how symlinks are setup into the cache on Windows
Upgrades inquirer
, fixing upgrade-interactive
for users using both Node 10 and Windows
Exposes the path to the PnP file using require.resolve('pnpapi')
Changelog
1.12.1
Ensures the engine check is ran before showing the UI for upgrade-interactive
Restores Node v4 support by downgrading cli-table3
Prevents infinite loop when parsing corrupted lockfiles with unterminated strings
Environment variables now have to start with YARN_
(instead of just contain it) to be considered
Fixes the extensions
option when used by resolveRequest
Fixes handling of empty string entries for bin
in package.json
Adds support for basic auth for registries with paths, such as artifactory
Adds 2FA (Two Factor Authentication) support to publish & alike
Fixes how the files
property is interpreted to bring it in line with npm
Fixes Yarn invocations on Darwin when the yarn
binary was symlinked
Fixes require.resolve
when used together with the paths
option
Changelog
1.12.0
Adds initial support for PnP on Windows
Adds yarn audit
(and the --audit
flag for all installs)
Adds a special logic to PnP for ESLint compatibility (temporary, until eslint/eslint#10125 is fixed)
Makes the PnP hook inject a process.versions.pnp
variable when setup (equals to VERSIONS.std
)
Disables by default (configurable) the automatic migration of the integrity
field. It will be re-enabled in 2.0.
Fixes the display name of the faulty package when the NPM registry returns corrupted data
Prevents crashes when running yarn outdated
and the NPM registry forgets to return the latest
tag
Fixes yarn run
when used together with workspaces and PnP
Fixes an edge case when peer dependencies were resolved multiple levels deep (webpack-dev-server
)