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.json
field:peerDependenciesMeta
-
Adds an
optional
settings topeerDependenciesMeta
to 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
main
entry -
Decreases the size of the generated
$PATH
environment 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
resolve
package 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 audit
when using workspaces -
Uses
NODE_OPTIONS
to 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 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
, fixingupgrade-interactive
for 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
extensions
option when used byresolveRequest
-
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 thepaths
option