Settings (.yarnrc.yml)
Yarnrc files (named this way because they must be called .yarnrc.yml) are the one place where you'll be able to configure Yarn's internal settings. While Yarn will automatically find them in the parent directories, they should usually be kept at the root of your project (often your repository). Starting from the v2, they must be written in valid Yaml and have the right extension (simply calling your file .yarnrc won't do).
Environment variables can be accessed from setting definitions by using the ${NAME} syntax when defining the values. By default Yarn will require the variables to be present, but this can be turned off by using either ${NAME-fallback} (which will return fallback if NAME isn't set) or ${NAME:-fallback} (which will return fallback if NAME isn't set, or is an empty string).
Finally, note that most settings can also be defined through environment variables (at least for the simpler ones; arrays and objects aren't supported yet). To do this, just prefix the names and write them in snake case: YARN_CACHE_FOLDER will set the cache folder (such values will overwrite any that might have been defined in the RC files - use them sparingly).
cacheFolder
Path where the downloaded packages are stored on your system.
They'll be normalized, compressed, and saved under the form of zip archives with standardized names. The cache is deemed to be relatively safe to be shared by multiple projects, even when multiple Yarn instances run at the same time on different projects. For setting a global cache folder, you should use enableGlobalCache instead.
cacheMigrationMode
Behavior that Yarn should follow when it detects that a cache entry is outdated.
Whether or not a cache entry is outdated depends on whether it has been built and checksumed by an earlier release of Yarn, or under a different compression settings. Possible behaviors are:
- If
required-only, it'll keep using the file as-is, unless the version that generated it was decidedly too old. - If
match-spec, it'll also rebuild the file if the compression level has changed. - If
always(the default), it'll always regenerate the cache files so they use the current cache version.
httpsCaFilePath
Path to a file containing one or multiple Certificate Authority signing certificates.
changesetBaseRefs
List of git refs against which Yarn will compare your branch when it needs to detect changes.
Supports git branches, tags, and commits. The default configuration will compare against master, origin/master, upstream/master, main, origin/main, and upstream/main.
changesetIgnorePatterns
Array of file glob patterns that will be excluded from change detection.
Files matching the following patterns (in terms of relative paths compared to the root of the project) will be ignored by every command checking whether files changed compared to the base ref (this include both yarn version check and yarn workspaces foreach --since).
checksumBehavior
Behavior that Yarn should follow when it detects that a cache entry has a different checksum than expected.
Possible behaviors are:
- If
throw(the default), Yarn will throw an exception. - If
update, the lockfile will be updated to match the cached checksum. - If
reset, the cache entry will be purged and fetched anew. - If
ignore, nothing will happen, Yarn will skip the check.
cloneConcurrency
Amount of git clone operations that Yarn will run at the same time.
We by default limit it to 2 concurrent clone operations.
compressionLevel
Compression level employed for zip archives
Possible values go from 0 ("no compression, faster") to 9 ("heavy compression, slower"). The value mixed is a variant of 9 where files are stored uncompressed if the gzip overhead would exceed the size gain.
The default is 0, which tends to be significantly faster to install. Projects using zero-installs are advised to keep it this way, as experiments showed that Git stores uncompressed package archives more efficiently than gzip-compressed ones.
constraintsPath
Path of the constraints file.
This only matters for Prolog constraints, which are being deprecated. JavaScript constraints will always be read from the yarn.config.cjs file.
defaultLanguageName
Default language mode that should be used when a package doesn't offer any insight.
This is an internal configuration setting that shouldn't be touched unless you really know what you're doing.
defaultProtocol
Default protocol that should be used when a dependency range is a pure semver range.
This is an internal configuration setting that shouldn't be touched unless you really know what you're doing.
defaultSemverRangePrefix
Default prefix used in semver ranges created by yarn add and similar commands.
Possible values are "^" (the default), "~" or "".
deferredVersionFolder
Folder where the versioning files are stored.
enableColors
Define whether colors are allowed on the standard output.
The default is to check the terminal capabilities, but you can manually override it to either true or false.
enableConstraintsChecks
Define whether constraints should run on every install.
If true, Yarn will run your constraints right after finishing its installs. This may help decrease the feedback loop delay by catching errors long before your CI would even report them.
enableGlobalCache
Define whether the cache should be shared between all local projects.
If true (the default), Yarn will store the cache files into a folder located within globalFolder instead of respecting cacheFolder.
enableHardenedMode
Define whether Yarn should attempt to check for malicious changes.
If true, Yarn will query the remote registries to validate that the lockfile content matches the remote information. These checks make installs slower, so you should only run them on branches managed by users outside your circle of trust.
Yarn will automatically enable the hardened mode on GitHub pull requests from public repository. Should you want to disable it, explicitly set it to false in your yarnrc file.
enableHyperlinks
Define whether hyperlinks are allowed on the standard output.
The default is to check the terminal capabilities, but you can manually override it to either true or false.
enableImmutableCache
Define whether to allow adding/removing files from the cache or not.
If true, Yarn will refuse to change the cache in any way, whether it would add files or remove them, and will abort installs instead of letting that happen.
enableImmutableInstalls
Define whether to allow adding/removing entries from the lockfile or not.
If true (the default on CI), Yarn will refuse to change the lockfile in any way, whether it would add new entries or remove them. Other files can be added to the checklist via the immutablePatterns setting.
enableInlineBuilds
Define whether to print the build output directly within the terminal or not.
If true (the default on CI environments), Yarn will print the build output directly within the terminal instead of buffering it in an external log file. Note that by default Yarn will attempt to use collapsible terminal sequences on supporting CI providers to make the output more legible.
enableInlineHunks
Define whether to print patch hunks directly within the terminal or not.
If true, Yarn will print any patch sections (hunks) that could not be applied successfully to the terminal.
enableMessageNames
Define whether to prepend a message name before each printed line or not.
If true, Yarn will prefix most messages with codes suitable for search engines, with hyperlink support if your terminal allows it.
enableMirror
Define whether to mirror local cache entries into the global cache or not.
If true (the default), Yarn will use the global folder as indirection between the network and the actual cache. This is only useful if enableGlobalCache is explicitly set to false, as otherwise the cache entries are persisted to the global cache no matter what.
enableNetwork
Define whether remote network requests are allowed or not.
If false, Yarn will never make any request to the network by itself, and will throw an exception rather than let it happen. It's a very useful setting for CI, which typically want to make sure they aren't loading their dependencies from the network by mistake.
enableOfflineMode
Define whether Yarn should exclusively read package metadata from its cache
If true, Yarn will replace any network requests by reads from its local caches - even if they contain old information. This can be useful when performing local work on environments without network access (trains, planes, ...), as you can at least leverage the packages you installed on the same machine in the past.
Since this setting will lead to stale data being used, it's recommended to set it for the current session as an environment variable (by running export YARN_ENABLE_OFFLINE_MODE=1 in your terminal) rather than by adding it to your .yarnrc.yml file.
enableProgressBars
Define whether animated progress bars should be shown or not.
If true (the default outside of CI environments), Yarn will show progress bars for long-running events.
enableScripts
If false, Yarn will not execute the postinstall scripts from third-party packages when installing the project (workspaces will still see their postinstall scripts evaluated, as they're assumed to be safe if you're running an install within them).
Note that you also have the ability to disable scripts on a per-package basis using dependenciesMeta, or to re-enable a specific script by combining enableScripts and dependenciesMeta.
enableStrictSsl
Define whether SSL errors should fail requests or not.
If false, SSL certificate errors will be ignored
enableTelemetry
Define whether anonymous telemetry data should be sent or not.
If true (the default outside of CI environments), Yarn will periodically send anonymous data to our servers tracking some usage information such as the number of dependencies in your project, how many installs you ran, etc.
Consult the Telemetry page for more details about this process.
enableTimers
Define whether to print the time spent running each sub-step or not.
If false, Yarn will not print the time spent running each sub-step when running various commands. This is only needed for testing purposes, when you want each execution to have exactly the same output as the previous ones.
enableTransparentWorkspaces
Define whether pure semver ranges should allow workspace resolution or not.
If false, Yarn won't link workspaces just because their versions happen to match a semver range. Disabling this setting will require all workspaces to reference one another using the explicit workspace: protocol.
This setting is usually only needed when your project needs to use the published version in order to build the new one (that's for example what happens with Babel, which depends on the latest stable release to build the future ones).
globalFolder
Path where all files global to the system will be stored.
Various files we be stored there: global cache, metadata cache, ...
httpProxy
Proxy to use when making an HTTP request.
Only HTTP proxies are supported at the moment.
httpRetry
Amount of time to wait in seconds before retrying a failed HTTP request.
httpTimeout
Amount of time to wait in milliseconds before cancelling pending HTTP requests.
httpsCertFilePath
Path to a file containing a certificate chain in PEM format.
httpsKeyFilePath
Path to a file containing a private key in PEM format.
httpsProxy
Define a proxy to use when making an HTTPS request.
Only HTTP proxies are supported at the moment.
ignorePath
Define whether yarnPath should be respected or not.
If true, whatever Yarn version is being executed will keep running rather than looking at the value of yarnPath to decide.
immutablePatterns
Array of file patterns whose content won't be allowed to change if enableImmutableInstalls is set.
initScope
Scope used when creating packages via the init command.
initFields
Additional fields to set when creating packages via the init command.
injectEnvironmentFiles
Array of .env files which will get injected into any subprocess spawned by Yarn.
By default Yarn will automatically inject the variables stored in the .env.yarn file, but you can use this setting to change this behavior.
Note that adding a question mark at the end of the path will silence the error Yarn would throw should the file be missing, which may come in handy when declaring local configuration files.
installStatePath
Path where the install state will be persisted.
The install state file contains a bunch of cached information about your project. It's only used for optimization purposes, and will be recreated if missing (you don't need to add it to Git).
logFilters
Alter the log levels for emitted messages.
This can be used to hide specific messages, or instead make them more prominent. Rules defined there accept filtering messages by either name or raw content.
logFilters.code
Match all messages with the given code.
logFilters.level
New log level to apply to the matching messages. Use discard if you wish to hide those messages altogether.
logFilters.text
Match messages whose content is strictly equal to the given text.
In case a message matches both code-based and text-based filters, the text-based ones will take precedence over the code-based ones.
logFilters.level
New log level to apply to the matching messages. Use discard if you wish to hide those messages altogether.
logFilters.pattern
Match messages whose content match the given glob pattern.
In case a message matches both pattern-based and code-based filters, the pattern-based ones will take precedence over the other ones. Patterns can be overridden on a case-by-case basis by using the text filter, which has precedence over pattern.
logFilters.level
New log level to apply to the matching messages. Use discard if you wish to hide those messages altogether.
networkConcurrency
Amount of HTTP requests that are allowed to run at the same time.
We default to 50 concurrent requests, but it may be required to limit it even more when working behind proxies that can't handle large amounts of traffic.
networkSettings
Additional network settings, per hostname
nmHoistingLimits
Highest point where packages can be hoisted.
Replacement of the former nohoist setting. Possible values are:
- If
none(the default), packages are hoisted as per the usual rules. - If
workspaces, packages won't be hoisted past the workspace that depends on them. - If
dependencies, transitive dependencies also won't be hoisted past your direct dependencies.
This setting can be overridden on a per-workspace basis using the installConfig.hoistingLimits field.
nmSelfReferences
Define whether workspaces are allowed to require themselves.
If false, Yarn won't create self-referencing symlinks when using nodeLinker: node-modules. This setting can be overridden on a per-workspace basis using the installConfig.selfReferences field.
nmMode
Define how to copy files to their target destination.
Possible values are:
- If
classic, regular copy or clone operations are performed. - If
hardlinks-global, hardlinks to a global content-addressable store will be used. - If
hardlinks-local, hardlinks will only be created between similar packages from the same project.
For compatibility with the ecosystem, the default is classic.
nodeLinker
Define how Node packages should be installed.
Yarn supports three ways to install your project's dependencies, based on the nodeLinker setting. Possible values are:
- If
pnp, a single Node.js loader file will be generated. - If
pnpm, anode-moduleswill be created using symlinks and hardlinks to a global content-addressable store. - If
node-modules, a regularnode_modulesfolder just like in Yarn Classic or npm will be created.
winLinkType
Define whether to use junctions or symlinks when creating links on Windows.
Possible values are:
- If
junctions, Yarn will use Windows junctions when linking workspaces intonode_modulesdirectories, which are always absolute paths. - If
symlinks, Yarn will use symlinks, which will use relative paths, and is consistent with Yarn's behavior on non-Windows platforms.
Symlinks are preferred, but they require the Windows user running Yarn to have the create symbolic links privilege. As a result, we default to using junctions instead.
npmAlwaysAuth
Define whether to always send authentication credentials when querying the npm registry.
If true, authentication credentials will always be sent when sending requests to the registries. This shouldn't be needed unless you configured the registry to reference a private npm mirror.
npmAuditRegistry
Define the registry to use when auditing dependencies.
If not explicitly set, the value of npmRegistryServer will be used.
npmAuthIdent
Define the authentication credentials to use by default when accessing your registries.
Replacement of the former _auth setting. Because it requires storing unencrypted values in your configuration, npmAuthToken should be preferred when possible.
npmAuthToken
Define the authentication token to use by default when accessing your registries.
Replacement of the former _authToken settings. If you're using npmScopes to define multiple registries, the npmRegistries dictionary allows you to override these credentials on a per-registry basis.
npmPublishAccess
Define the default access to use when publishing packages to the npm registry.
Valid values are public and restricted, but restricted usually requires to register for a paid plan (this is up to the registry you use). Can be overridden on a per-package basis using the publishConfig.access field.
npmAuditExcludePackages
Array of advisory ID glob patterns of packages to exclude from yarn npm audit.
npmAuditIgnoreAdvisories
Array of advisory ID glob patterns to ignore from yarn npm audit results.
npmPublishRegistry
Define the registry to use when pushing packages.
If not explicitly set, the value of npmRegistryServer will be used. Overridden by publishConfig.registry.
npmRegistries
Per-registry configurations.
npmRegistryServer
Define the registry to use when fetching packages.
Should you want to define different registries for different scopes, see npmScopes. To define the authentication scheme for your servers, see npmAuthToken. The url must use HTTPS by default, but this can be changed by adding it to the unsafeHttpWhitelist.
npmScopes
Per-scope registry configurations.
packageExtensions
Extend the package definitions of your dependencies; useful to fix third-party issues.
Some packages may have been specified incorrectly with regard to their dependencies - for example with one dependency being missing, causing Yarn to refuse it the access. The packageExtensions fields offer a way to extend the existing package definitions with additional information. If you use it, consider sending a PR upstream and contributing your extension to the plugin-compat database.
Note: This field is made to add dependencies; if you need to rewrite existing ones, prefer the resolutions field instead.
patchFolder
Folder where patch files will be written to.
pnpEnableEsmLoader
Define whether to generate a Node.js ESM loader or not.
If true, Yarn will generate an experimental ESM loader (.pnp.loader.mjs) on top of the CJS one.
pnpEnableInlining
Define whether to store the PnP data in the generated file or not.
If false, Yarn will generate an additional .pnp.data.json file.
pnpFallbackMode
Define whether to allow packages to rely on the builtin PnP fallback mechanism.
Possible values are:
- If
all, all packages can access dependencies made available in the fallback. - If
dependencies-only(the default), dependencies will have access to them but not your workspaces. - If
none, no packages will have access to them.
pnpIgnorePatterns
Array of file glob patterns that should be forced to use the default CommonJS resolution.
Files matching those locations will not be covered by PnP and will use the regular Node.js resolution algorithm. Typically only needed if you have subprojects that aren't yet part of your workspace tree.
pnpMode
Define whether to attempt to simulate traditional node_modules hoisting.
Possible values are:
- If
strict(the default), modules won't be allowed to require packages they don't explicitly list in their own dependencies. - If
loose, packages will be allowed to access any other package that would have been hoisted to the top-level under 1.x installs.
Note that, even in loose mode, hoisted require calls are unsafe and should be discouraged.
pnpShebang
String prepended to the generated PnP loader.
pnpUnpluggedFolder
Path where unplugged packages are stored.
While Yarn attempts to reference and load packages directly from their zip archives, it may not always be possible. In those cases, Yarn will extract the files to the unplugged folder.
preferDeferredVersions
Define whether to use deferred versioning by default or not.
If true, deferred versioning by default when running the yarn version family of commands.
preferInteractive
Define whether to use interactive prompts by default or not.
If true, Yarn will ask for your guidance when some actions would be improved by being disambiguated. Enabling this setting also unlocks some features (for example the yarn add command will suggest to reuse the same dependencies as other workspaces if pertinent).
preferReuse
Define whether to reuse most common dependency ranges or not when adding dependencies to a package.
If true, yarn add will attempt to reuse the most common dependency range in other workspaces.
preferTruncatedLines
Define whether to truncate lines that would go beyond the size of the terminal or not.
If true, Yarn will truncate lines that would go beyond the size of the terminal. If progress bars are disabled, lines will never be truncated.
progressBarStyle
Style of progress bar to use.
supportedArchitectures
Systems for which Yarn should install packages.
supportedArchitectures.os
List of operating systems to cover.
supportedArchitectures.cpu
List of CPU architectures to cover.
See https://nodejs.org/docs/latest/api/process.html#processarch for the architectures supported by Node.js
supportedArchitectures.libc
The list of standard C libraries to cover.
taskPoolConcurrency
Maximal amount of concurrent heavy task processing.
We default to the platform parallelism, but for some CI, os.cpus may not report accurate values and may overwhelm their containers.
workerPoolMode
Execution strategy for heavy tasks.
By default will use workers when performing heavy tasks, such as converting tgz files to zip. This setting can be used to disable workers and use a regular in-thread async processing.
telemetryInterval
Define the minimal amount of time between two telemetry events, in days.
By default we only send one request per week, making it impossible for us to track your usage with a lower granularity.
telemetryUserId
User-defined unique ID to send along with telemetry events.
The default settings never assign unique IDs to anyone, so we have no way to know which data originates from which project. This setting can be used to force a user ID to be sent to our telemetry server.
Frankly, it's only useful in some very specific use cases. For example, we use it on the Yarn repository in order to exclude our own usage from the public dashboards (since we run Yarn far more often here than anywhere else, the resulting data would be biased).
tsEnableAutoTypes
Define whether to automatically install @types dependencies.
If true, Yarn will automatically add @types dependencies when running yarn add with packages that don't provide their own typings (as reported by the Algolia npm database). This behavior is enabled by default if you have a tsconfig.json file at the root of your project, or in your current workspace.
unsafeHttpWhitelist
Array of hostname glob patterns for which using the HTTP protocol is allowed.
virtualFolder
Path where virtual packages will be stored.
Due to a particularity in how Yarn installs packages which list peer dependencies, some packages will be mapped to multiple virtual directories that don't actually exist on the filesystem. This settings tells Yarn where to put them. Note that the folder name must be __virtual__.
yarnPath
Path of a Yarn binary to use instead of the global one.
This binary will be executed instead of any other (including the global one) for any command run within the directory covered by the rc file. If the file extension ends with .js it will be required, and will be spawned in any other case.
The yarnPath setting used to be the preferred way to install Yarn within a project, but we now recommend to use Corepack in most cases.