Releases: yarnpkg/yarn
v1.16.0
v1.15.2
v1.15.1
v1.15.0
v1.14.0
v1.13.0
-
Implements a new
package.jsonfield:peerDependenciesMeta -
Adds an
optionalsettings topeerDependenciesMetato silence missing peer dependency warnings -
Implements
yarn policies set-version [range]. Check the documentation for usage & tips. -
Fixes a resolution issue when a package had an invalid
mainentry -
Decreases the size of the generated
$PATHenvironment variable for a better Windows support -
Fixes postinstall scripts for third-party packages when they were referencing a binary from their own dependencies
-
Fixes yarn audit exit code overflow
-
Stops automatically unplugging packages with postinstall script when running under
--ignore-scripts -
Adds transparent support for the
resolvepackage when using Plug'n'Play -
Properly reports the error codes when the npm registry throws 500's
v1.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 auditwhen using workspaces -
Uses
NODE_OPTIONSto instruct Node to load the PnP hook, instead of raw CLI argumentsCaveat: 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 auditwhen the root package was missing a name -
Fixes an issue with
yarn auditwhen a package was depending on an empty range -
Fixes an issue with how symlinks are setup into the cache on Windows
-
Upgrades
inquirer, fixingupgrade-interactivefor users using both Node 10 and Windows -
Exposes the path to the PnP file using
require.resolve('pnpapi')
v1.12.2
v1.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
extensionsoption when used byresolveRequest -
Fixes handling of empty string entries for
binin 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
filesproperty is interpreted to bring it in line with npm -
Fixes Yarn invocations on Darwin when the
yarnbinary was symlinked -
Fixes
require.resolvewhen used together with thepathsoption
v1.12.0
-
Adds initial support for PnP on Windows
-
Adds
yarn audit(and the--auditflag 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.pnpvariable when setup (equals toVERSIONS.std) -
Disables by default (configurable) the automatic migration of the
integrityfield. 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 outdatedand the NPM registry forgets to return thelatesttag -
Fixes
yarn runwhen used together with workspaces and PnP -
Fixes an edge case when peer dependencies were resolved multiple levels deep (
webpack-dev-server)