chore(deps): update yarn to v4 #78
Loading…
Reference in New Issue
No description provided.
Delete Branch "renovate/major-yarn-monorepo"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
3.6.4
->4.0.1
Release Notes
yarnpkg/berry (yarn)
v4.0.1
Compare Source
node-modules
linker when inner workspace depends on outer workspaceyarn npm audit --ignore NUM
which didn't apply to deprecationsyarn npm audit --json
which didn't print the right output format@yarnpkg/core
yarn explain peer-requirements
commandv4.0.0
Compare Source
Major Changes
With Node.js 16's now being End of Life'd, we dropped support for Node.js versions lower than 18.12.
Some important defaults have changed:
yarn init
andyarn set version
will prefer usingpackageManager
rather thanyarnPath
when possible (when they detectCOREPACK_ROOT
in your environment variables).yarn init
will no longer use zero-install by default. You still can enable it, but it should make it easier to start one-of projects without having to rewrite the configuration afterwards.enableGlobalCache
now defaults totrue
. If your project uses Zero-Installs, the firstyarn install
you run after migrating to 4.0 will automatically setenableGlobalCache: false
in your local.yarnrc.yml
.yarn workspaces foreach
now requires one of--all
,--recursive
,--since
, or--worktree
to be explicitly specified; the previous default was--worktree
, but it was rarely what users expected.compressionLevel
now defaults to0
rather thanmixed
. It's been proved significantly faster on installs, and the size impact was reasonable enough to change the default. Note that it benefits you even if you use Zero-Installs: as per our tests, a zero-compression is actually easier to handle for Git (you can see by yourself with those examples usingcompressionLevel: 0
vscompressionLevel: mixed
).yarn install
after migrating from 3.6 to 4.0. If you do, it will automatically set the old default (compressionLevel: mixed
) in your.yarnrc.yml
file. You can then remove it whenever you feel ready to actually change the compression settings.All official Yarn plugins are now included by default in the bundle we provide. You no longer need to run
yarn plugin import
for official plugins (you still need to do it for third-party plugins, of course).Yarn's UI during installs has been greatly improved:
node-gyp
and transitive peer dependency errors) have been removed.yarn rebuild
calls.yarn npm audit
.Some settings were renamed or removed:
caFilePath
is nowhttpsCaFilePath
preferAggregateCacheInfo
has been removed (it's now always on)pnpDataPath
has been removed to adhere to our new PnP specification. For consistency, all PnP files will now be hardcoded to a single value so that third-party tools can implement the PnP specification without relying on the Yarn configuration.The
yarn npm audit
command has been reimplemented:/-/npm/v1/security/advisories/bulk
endpoint.npmAuditRegistry
can be used to temporarily route audit queries to the npm registry.yarn npm audit ! --no-deprecations
.Some legacy layers have been sunset:
.pnp.js
file when migrating.--assume-fresh-project
flag ofyarn init
has been removed.API Changes
The following changes only affect people writing Yarn plugins:
The
ZipFS
andZipOpenFS
classes have been moved from@yarnpkg/fslib
to@yarnpkg/libzip
. They no longer need or accept thelibzip
parameter.open
,ZIP_CREATE
, andZIP_TRUNCATE
bindings are no longer needed forZipFS
and have also been removed.The
dependencies
field sent returned byResolver#resolve
must now be the result of aConfiguration#normalizeDependencyMap
call. This change is prompted by a refactoring of how default protocols (ienpm:
) are injected into descriptors. The previous implementation caused various descriptors to never be normalized, which made it difficult to know what were the descriptors each function should expect.Similarly, the descriptors returned by
Resolve#getResolutionDependencies
are now expected to be the result ofConfiguration#normalizeDependency
calls.Note that this only applies to the
dependencies
field; thepeerDependencies
field is unchanged, as it must only contains semver ranges without any protocol (with an exception forworkspace:
, but that's not relevant here).The
Resolve#getResolutionDependencies
function must now return an object of arbitrary string keys and descriptor values (instead of a map withDescriptorHash
keys). Those descriptors will be resolved and assigned to the same keys as the initial object. This change allows resolvers to wrap resolution dependencies from other resolvers, which wasn't possible before since it'd have caused the key to change.The
generateLoader
function in@yarnpkg/pnp
no longer generates the$$SETUP_STATE
function, it now needs to be present in theloader
passed to the function.The
getCustomDataKey
function inInstaller
from@yarnpkg/core
has been moved toLinker
.renderForm
'soptions
argument is now required to enforce that custom streams are always specified.npmConfigUtils.getAuditRegistry
no longer takes aManifest
as its first argument.The
FetchOptions.skipIntegrityCheck
option has been removed. UseFetchOptions.cacheOptions.skipIntegrityCheck
instead.MapConfigurationValue
has been removed. UsemiscUtils.ToMapValue
instead.Manifest.isManifestFieldCompatible
andManifest.prototype.isCompatibleWith{OS,CPU}
have been removed. UseManifest.prototype.getConditions
andstructUtils.isPackageCompatible
instead.versionUtils.{fetchBase,fetchRoot,fetchChangedFiles}
have been moved from@yarnpkg/plugin-version
to@yarnpkg/plugin-git
. UsegitUtils.{fetchBase,fetchRoot,fetchChangedFiles}
instead.For consistency reasons:
Link{Resolver,Fetcher}
have been renamed toPortal{Resolver,Fetcher}
RawLink{Resolver,Fetcher}
have been renamed toLink{Resolver,Fetcher}
FakeFS
classes are now required to implementlutimes{Sync,Promise}
.workspace.dependencies
has been removed. Useworkspace.anchoredPackage.dependencies
instead.The
Installer
class must now returnBuildRequest
structures instead ofBuildDirective[]
. This lets you mark that the build must be skipped, and the reason why.startCacheReport
has been removed, and is now part of the output generated byfetchEverything
.forgettableNames
&forgettableBufferSize
have been removed (the only messages using them have been removed, making the forgettable logs implementation obsolete).workspace.locator
has been removed. You can instead use:workspace.anchoredLocator
to get the locator that's used throughout the dependency tree.workspace.manifest.version
to get the workspace version.configuration.{packageExtensions,refreshPackageExtensions}
have been removed. Useconfiguration.getPackageExtensions
instead.configuration.normalizePackage
now requires apackageExtensions
option.ProjectLookup
has been removed. BothConfiguration.find
andConfiguration.findProjectCwd
now always do a lockfile lookup.Installs
pnpm
linker avoids creating symlinks that lead to loops on the file system, by moving them higher up in the directory structure.pnpm
linker no longer reports duplicate "incompatible virtual" warnings.Features
enableOfflineMode
is a new setting that, when set, will instruct Yarn to only use the metadata and archives already stored on the local machine rather than download them from the registry. This can be useful when performing local development under network-constrained environments (trains, planes, ...).yarn run bin
now injects the environment variables defined in.env.yarn
when spawning a process. This can be configured using theinjectEnvironmentFiles
variable.yarn workspaces foreach
now automatically enables theyarn workspaces foreach ! --verbose
flag in interactive terminals.Bugfixes
yarn dlx
will no longer report false-positiveUNUSED_PACKAGE_EXTENSION
warningsyarn workspace
will now set$INIT_CWD
to the CLI working directory rather than the workspace root.Shell
Compatibility
FileHandle.readLines
.Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.
61afe7eb52
to5af89eb890
5af89eb890
to758142bf59
758142bf59
tof867c76edc
f867c76edc
tod08e82d285
d08e82d285
to10f91a2c83
10f91a2c83
to14654e1b28
14654e1b28
toee95f56ce4
ee95f56ce4
toff193859ac
ff193859ac
to3ca06df8ff
3ca06df8ff
to1567bf922d
1567bf922d
to36e2222e77
36e2222e77
to39dfd46ee0
39dfd46ee0
to6e971c6f45
6e971c6f45
to691bc9f71f
691bc9f71f
to29643e550b
29643e550b
to8f66f74679
8f66f74679
toa483b6aa60
a483b6aa60
to27992aa4d6