@yarnpkg/parsers

yarn set version 2.4.1

Compatibility

• The release of TypeScript 4.2 couldn't be installed due to patch conflicts. This is now fixed. This version only includes a fix specific to 4.2, but future Yarn releases starting from 3.0 will be more tolerant of this kind of situation and won't cause such errors.

yarn set version 2.4.0

Installs

• The resolution pipeline got reimplemented. We previously used a multi-pass approach where we performed SAT optimization between each pass, but after investigating it turned out the SAT optims had little impact and added performance bottlenecks. We now run the resolution using a much simpler and more efficient algorithm.

• Linkers can now define custom data to cache between Yarn invocations. The builtin linkers new use those new capabilities to cache package information that can't change between runs. In practice, this translates into much faster recurrent installs (when running an install that adds few new packages, if any).

• Warnings are now reported when packageExtensions rules are either unused or redundant with the original package definition.

• Potentially breaking, but it was intended this way from the start: the packageExtensions field cannot be used to replace dependencies anymore (only to add missing ones). Prefer using the resolutions field to replace existing ones.

• Progress bars are rendered less often, which should help performances on some terminals.

• Aliased packages no longer include themselves in node_modules installs

CLI

• The upgrade-interactive command will now only show upgrade suggestions for packages that have available upgrades (rather than all of them).

• The upgrade-interactive command has received UI improvements that should make it easier to look at.

• The yarn workspaces focus command will now only run the postinstall scripts for the focused workspaces.

• A new yarn npm audit command lets you query audit information from the npm registry.

• The yarn workspaces foreach command has a new flag, -R,--recursive, which will run a command on the current workspace and all others it depends on.

• A new --skip-builds option on yarn install will let you skip the build scripts without impacting the generated Yarn artifacts (contrary to enableScripts, which would also stop unplugging the packages that would otherwise be unplugged due to containing build scripts).

Binaries

• It's now possible to run dependency binaries when using the node-modules linker even if one of your other dependencies is reported as incompatible with your system.

• By default Windows automatically requests for administrator rights before spawning any binary whose filename contains "install", "setup", "update", or "patch" (it thinks they are installers). We now explicitly opt-out of this behavior in the binary jumpers we use on Windows.

• By default, arguments passed to MinGW-compiled programs are automatically expanded by a basic glob pattern engine. We now explicitly opt-out of this behavior in the binary jumpers we use on Windows.

• The Windows binary jumpers will now report the right exit code.

Settings

• Using empty fallbacks in Yarnrc environment variables (${VAR:-}) will now work.

• You can now use the new logFilters setting to turn warnings into either errors or info, or to hide them entirely. Note that we plan to significantly improve the peer dependency warnings in the next release, so perhaps don't silence them just now even if you have a bunch of them.

Shell

• Some shell errors (No matches found, Bad file descriptor, Unbound variable, Unbound argument) will now be recoverable errors that make the shell continue on to the next command in the chain instead of hard crashes. Fixes cases such as rm -rf ./inexistentFolder/* || true.

VSCode ZipFS Extension

• The extension will now activate even if the workspace doesn't contain zip files (usually because you excluded them).

Compatibility

• Some patches went missing for TypeScript <4. This is now fixed.

• Calling fs.exists(undefined) won't crash anymore.

• TypeScript import suggestions should now be correct even when the imported module is deep within a workspace.

• TypeScript in watch mode (both using -w and within VSCode) will now detect new dependencies as you add them.

• Some particular multi-dependency-trees setups will be better supported on Plug'n'Play installs.

• Using ctrl+click on imports in VSCode won't take you to virtual packages anymore (require an SDK update).

yarn set version 2.3.0

CLI

• The yarn tag set of commands has been ported over from Yarn Classic as yarn npm tag.
• Running yarn info will now print many information about your dependencies. Various options are available to tweak the output, including --json. Plugin authors can provide their own information sections via the fetchPackageInfo hook.
• Running yarn stage with the -r,--reset flag will now unstage all changes that seem related to Yarn.
• All commands now document each of their options (run yarn add -h to see an example).
• Publish registry errors will now be reported as is rather than being collapsed into a generic error message.
• A native binary jumper will now be used on Windows to avoid the Terminate batch job (Y/N)? prompts when invoking dependency binaries.

Installs

PnP API

The following changes only apply to the pnp linker (which is the default install strategy):

• The pnpapi module now exposes a new function called getAllLocators allow you to access the list of all locators in the map without having to traverse the dependency tree. This method is considered a Yarn extension, so you should check for its existence if you plan to use it in your code.
• When using a portal to a package that had peer dependencies, Yarn would loose the information required to resolve those peer dependencies. It will now properly resolve them the same way as all other packages in the dependency tree.

The following changes only apply to the node-modules linker:

• The bin symlinks will now be properly removed from the node_modules/.bin folder as their corresponding dependencies are removed.
• A new setting called nmHoistingLimits has appeared. It replaces what was previously known as nohoist in Yarn 1.
• We are now more forgiving for packages that make incorrect assumptions about the hoisting layout by first trying to maximize package exposure at the top-level. Only after the top-level has been populated will we deduplicate the remaining packages.
• Fixed some pathological cases around peer dependencies. In particular, workspaces' peer dependencies will now be resolved against their closest workspace ancestor (according to the directory hierarchy) rather than be ignored. Note that peer dependencies are inherently problematic with workspaces when using the node-modules linker, and that the strictly correct behavior can only be obtained by using the default Plug'n'Play linker.
• Running install after an interrupted install is supported now and will result in a consistent install state

Shell

• Added support for $$ and $PPID
• Fixes some pathological globbing problems.

Bugfixes

• The yarn constraints --fix command will now properly persist the changes on disk.
• The yarn unplug command will now work when used on packages with peer dependencies.
• The yarn stage command will now allow to stage files when called without the -c,--commit flag.
• Fixes a performance regression when using FSEvents.

Miscellaneous

• Removes extraneous subprocesses when using the yarnPath setting.

Third-party integrations

• Updated the VSCode SDK to take into account changes in the TypeScript server protocol.
• Added a few builtin extensions to improve compatibility with packages that weren't correctly listing their dependencies.
• Updated the TypeScript patch to cover TypeScript 4.1.

yarn set version 2.2.0

Ecosystem

• Packages can now use the publishConfig.executableFiles field in their manifests to indicate which files should keep the executable flag once packed in the archive. This is important as for portability reasons Yarn strips the executable flag from all files during packing (otherwise yarn pack would yield different outputs when run on Posix vs Windows). Files listed in the bin field are assumed executable by default, so you don't need to explicitly list them in executableFiles.

Bugfixes

• Requests won't timeout anymore as long as the server is still sending data.
• yarn pack will properly include main/module/bin files, even when not explicitly referenced through the files field.
• Local git repositories can now be fetched via the git+file: protocol.
• The progress bars will be properly styled when using the new Windows terminal on certain days.
• Yarn will now avoid using deprecated versions of the dependencies, unless only deprecated versions are available for the requested ranges.
• Build keys are now properly computed, which fixes issues where build scripts weren't always triggered when they should have been.
• Negated glob patterns in the workspace field will now be processed correctly.
• Yarn will now allow relative paths inside the workspace: protocol to start with ./
• Yarn will now show the actual error when it fails to resolve a request during yarn add and yarn up
• The portable shell will now support calling cd and exit without arguments
• Yarn will now show the exit code when a lifecycle script fails
• Yarn's portable shell will now also pipe the stderr when using the |& pipeline
• Yarn's portable shell will now respect the left associativity of list operators

CLI

• Yarn will now report an error when run through an incompatible Node version.
• yarn add and yarn up will now respect the preferInteractive configuration option.
• yarn config set now supports the -H,--home flag, which causes it to update the home configuration instead of the project configuration.

Configuration

• The settings found in the home configuration file won't cause exceptions when consumed by older Yarn versions. Unsupported options will simply be silently ignored. This should improve the user experience when working with multiple projects configured with different Yarn versions.
• A new immutablePaths setting allow you to specify paths that must not change when running Yarn with the --immutable flag set. You can use it to detect unforeseen changes to your install artifacts, be it .pnp.js or node_modules files.

Miscellaneous

• Scripts can now use the $RANDOM variable as well as simple calculations using +, -, *, / and () inside $(())
• Scripts can now use grouping curly braces ({echo foo}) to execute a command in the context of the current shell (without creating a subshell like in the case of (echo foo)).
• Scripts can now end with a semicolon.
• PnP linker will not remove lingering node_modules inside folders matching pnpIgnorePatterns

Third-party integrations

• The PnP hook will now display clearer error message when requiring Node builtins from contexts that can't access them out of the box (for example when accessing the fs module from within a Webpack browser bundle).

yarn set version 2.1.0

Ecosystem

• Packages can now declare they they need to be unpacked in order to be functional using the new "preferUnplugged": true field in the manifest. This will hurt the experience of your users (your project will be the only one that will require hard installs), so please refrain using this field unless there's no other choice.

New commands

• Running yarn search will open a rich interface to search for packages to install (requires the interactive-tools plugin).
• Running yarn npm logout will remove your credentials from your home directory.
• Running yarn plugin import from sources will allow you to build plugins from the master branch of the our repository.
• Running yarn workspaces focus will only install the current workspace, plus any other workspace it might depend on. The --production flag will only install their production dependencies.
• Running yarn exec will execute the specified command at the root of the current workspace (reintroduced from the Classic branch).
• Running yarn create is now an alias to yarn dlx (with the create- prefix.)

CLI

• yarn init will now generate an EditorConfig file, and run git init on the resulting folder.
• yarn init now supports a -i flag which will automatically pin the Yarn version in the project.
• yarn init will now inject the settings from the initFields configuration setting when generating the initial manifest (future release will remove the now deprecated initVersion and initLicense settings).
• yarn init will now initialize a workspace project if given the -w flag.
• yarn workspaces foreach now support glob patterns in --include and --exclude.
• yarn set version now as an alias called yarn policies set-version (will be deprecated in 3.x).
• yarn run now supports the --inspect and --inspect-brk switches for binaries (for example yarn run --inspect-brk jest).
• yarn remove and yarn up now support glob patterns.
• yarn dlx now respects the local project configuration (particularly the configured registries). This is still experimental and will be further improved in the next months.
• yarn dlx now properly exits with an exit code when the underlying command returned an exit code too.
• yarn config get (and set) can now access nested configuration values (for example, yarn config get npmScopes.foo.npmRegistryServer will tell you which server is configured for the given server, if any).
• yarn config get will now hide its secrets (or rather yours) from the rest of the world. A new --no-redacted option will toggle off this behavior if needed.
• yarn config set now has a --json option that will let Yarn know it should interpret the given value as a JSON object (useful to set server configuration, etc).
• yarn workspace foreach will now exit with the expected status code if there's an error.

Configuration

• Registry auth settings can now be declared per-scope (they previously had to be per-registry). This will be handy with the GitHub Package Registry model, where each scope may have different access tokens.
• The configuration file now interpolates the values with the environment variables using the ${name} syntax (strict by default; use ${name:-default} to provide a default value).
• The new changesetIgnorePatterns setting can be used to ignore some paths from the changeset detection from yarn version check (changes to those paths won't be taken into account when deciding which workspaces need to fresh releases).
• The new changesetBaseRef setting can be used to change the name of the master branch that yarn version check will use in its changeset heuristic.
• The new httpTimeout and httpRetry settings allow you to configure the behavior of the HTTP(s) requests.
• The new preferTruncatedLines setting allow you to tell Yarn that it's ok if info and warning messages are truncated to fit in a single line (errors will always wrap as much as needed, and piping Yarn's output will toggle off this behaviour altogether).
• The cache compression level can now be configured through compressionLevel. If you don't use Zero-Installs, using a value of 0 may yield speed improvements at little cost.
• Plugins are now loaded from the location of the RC file.

Protocols

• The Git protocol has been improved, and now supports multiple patterns that were missing.
• The Git protocol can now clone any workspace from a given repository. To do this, use the owner/repo#workspace=name syntax (which you can mix with branch names as usual).
• The repositories cloned using the Git protocol will now automatically disable core.autocrlf so that the builds lead to deterministic results. Generally speaking, improvements have been made to avoid freshly built packages from generating different results.
• Packages fetched using the Git protocol will now be built using either of Yarn 1, Yarn 2, npm, or pnpm. The choice will be made based on the content of the sources (for example, we will pack the project using npm pack if we detect a package-lock.json).
• The exec: protocol has a different API. In particular, builtin modules can now be accessed without having to actually require them.

Installs

• Deprecation warnings are now shown during installs.
• The out-of-file PnP data generation has been fixed (it allows to generate the PnP data in a JSON file separated from the JS loader itself).
• An edge case in the virtual instances deduplication has been fixed; packages with the same effective peer dependencies now always share the exact same instance.
• The heuristic we use to locate zip files within paths has been improved. As a result, running ESLint on our repository now takes 28s instead of 57s.
• Yarn will now exclude the node_modules folder from the workspace detection. As a result, listing **/* in your workspaces field will now detect all child packages as workspaces.
• The cache names have changed in order to make the cache content-addressed. In particular, this mean that in the event where we need to fix a bug in the fetch steps, we won't need to bump a global cache key anymore.
• The PnP linker now features an additional loose mode (optional, and enabled through the pnpMode: loose setting). Under this mode, Yarn will compute the list of packages that would have been hoisted under the node_modules linker, and let the application code access them with only a warning. This mode will however not become the default - warnings cannot be caught by the application code, and as a result the output of the loose mode can be quite verbose, often being more confusing than the strict mode.
• Because we're aware of no incorrect hoisting bug on the v2 (but have discovered a few in the v1), and because its performances are about the same, the node_modules linker from Yarn 2 is now deemed more stable than the one from the v1, and we recommend users to migrate to it even if you don't want to use Plug'n'Play. More improvements are to come, but they'll mostly be in the user experience (for example to mix PnP and nm into a single install).

Rendering

• Rendering on small terminals (or terminals which didn't expose their size) could lead to failed assertions. This is now fixed.
• The output of yarn upgrade-interactive has been revamped to reintroduce some elements that had been omitted when porting the command from the v1 to the v2.
• Error codes are now hyperlinks on compatible terminals.

Third-party integrations

• The PnP hook will now display the list of packages that broke the peer dependency chain (it previously only showed the name of the package that wasn't provided the peer dependency, but not the name of which ancestor was responsible).
• We have added lutimes support into Node itself, since it was otherwise impossible to implement perfect copy mechanisms (the copied symlinks would end up with different mtime than their originals).
• The SDK files have been moved from .vscode/pnpify to .yarn/sdks.
• Improvements have been made in the VSCode integration. In particular, the PnP support is now good enough that it started to fix some longstanding issues that VSCode had with properly naming workspaces.
• We have contributed to VSCode support for third-party protocols with TypeScript. As a result, zip archives now properly support the "Jump to definition" workflow (this requires the ZipFS extension to be installed).
• The SDK output has been migrated to the same standard as the other commands.
• The SDK can now prepare the development environment for both VSCode and Vim. More third-party tools have been added, such as the Svelte extension. Note: the SDK is only needed for editor integrations; you don't need it if you just want to author JavaScript on basic text editors.

Miscellaneous

• Scripts can now use glob patterns, which will be resolved regardless of the underlying shell (so it'll work on Windows as well as Linux). Note that this only covers file globbing - using something like echo {foo,bar} won't work expect if there's actually a file named foo and/or bar.
• Sending SIGKILL (or other signals) to the Yarn process wasn't causing the child processes to stop. Yarn will now forward the signal, and wait for its children to exit.
• Some temporary folders weren't properly cleaned up; this has been fixed.
• Support for the .cjs extension has been added to multiple files in order to make it easier to use "type": "module".
• The bundle has received various size and startup time optimizations.

---