🚀 Breaking changes for Yarn 4
See original GitHub issueThis issue is just there to keep track of which changes we might want to do once we’ll get to the next major release. Doesn’t mean it’ll be anytime soon 🙂 Will be updated as time passes and we think about more things.
- https://github.com/yarnpkg/berry/pull/4196
- https://github.com/yarnpkg/berry/pull/4218
- https://github.com/yarnpkg/berry/pull/4262
- https://github.com/yarnpkg/berry/pull/4261 (Removes
yup) - https://github.com/yarnpkg/berry/pull/4252
- https://github.com/yarnpkg/berry/pull/4254
- https://github.com/yarnpkg/berry/pull/4302
- https://github.com/yarnpkg/berry/pull/4299
- https://github.com/yarnpkg/berry/pull/4305 (uses
npm:everywhere) - https://github.com/yarnpkg/berry/pull/4253
- https://github.com/yarnpkg/berry/pull/3004
- https://github.com/yarnpkg/berry/pull/3691
- https://github.com/yarnpkg/berry/pull/4320
- https://github.com/yarnpkg/berry/pull/4589
- https://github.com/yarnpkg/berry/pull/4834
- https://github.com/yarnpkg/berry/pull/4524
- https://github.com/yarnpkg/berry/pull/4982
- Make commands git-aware again
- Make
yarn initinitialize a git repository (already the case in 3.x) - Make
yarn versioncreate tags for the relevant workspaces
- Make
-
Installer['getCustomDataKey']: “Move this method intoLinkerso that linkers can use it to save some state useful to findPackageLocator (cf PnpmLinker).” - Make
ReportErrorlazily generate report messages when provided a configuration object by the streams; this would allow us to remove theconfigurationparameter from many helper functions where we only use it for display purposes. - Update
yarn workspaces foreachrecursive configuration; it’s not clear at the moment what should happen when-Rand--sinceare used together. Perhaps we’d need a--recursive-dependentsand--recursive-dependenciesflag? - https://github.com/yarnpkg/berry/pull/4595
- Cleanup https://github.com/yarnpkg/berry/pull/3612
- https://github.com/yarnpkg/berry/pull/4641
- Discuss the
fetchPackageFromCacheoptions bag.
- Transfer
arcanis.vscode-zipfsto the Yarnpkg org - Make Yarn detect whether it’s running inside a public repository (GitHub Actions) and, if it is AND the repository uses zero-installs, exit and recommend adding either
--check-cacheor--no-check-cache. - Write a formal spec for the PnP data files, so that 3rd-party resolvers (in particular native resolvers) can implement their own (originally I pushed for it to be a JS API so that we had more freedom to extend/correct the file format as needed, but in 3.x we didn’t need to change it so it might now be stable enough that we can relinquish some control).
- https://github.com/yarnpkg/berry/pull/4671
-
Consider only writing this data file by default, unless an option to generate an old-style(nope).pnp.cjsfile is set.
- https://github.com/yarnpkg/berry/pull/4503
- https://github.com/yarnpkg/berry/pull/4639
- https://github.com/yarnpkg/berry/pull/4644
- https://github.com/yarnpkg/berry/pull/4645
- https://github.com/yarnpkg/berry/pull/4648
- https://github.com/yarnpkg/berry/pull/4649
- https://github.com/yarnpkg/berry/pull/4697
- https://github.com/yarnpkg/berry/pull/4698
- https://github.com/yarnpkg/berry/pull/4773
- https://github.com/yarnpkg/berry/pull/4774
- https://github.com/yarnpkg/berry/pull/4865
- https://github.com/yarnpkg/berry/pull/4898
- https://github.com/yarnpkg/berry/pull/4899
Issue Analytics
- State:
- Created 2 years ago
- Reactions:58
- Comments:14 (4 by maintainers)
Top Results From Across the Web
Migration | Yarn - Package Manager
Any major release has its breaking changes, and Yarn 2 isn't the exception. A few old behaviors were cleaned, fixed, modified, or removed....
Read more >Yarn 3.0 🚀🤖 Performances, ESBuild, Better Patches
Breaking Changes. While the migration from Yarn 1 to Yarn 2 brought some discomfort, the migration to Yarn 3 should prove easier ...
Read more >Update Strapi version - Strapi Developer Docs
Upgrade Strapi version. Strapi periodically releases code improvements through upgrades. Upgrades contain no breaking changes and are announced in both the ...
Read more >Upgrading Storybook
Storybook upgrades are not the only thing to consider: changes in the ecosystem also present ... NextJS) have recently migrated from Webpack 4...
Read more >Node.js 15: What's new and how the developer experience ...
NPM now supports yarn.lock files. If present, this file will be used by NPM to determine where to fetch packages from. NPM will...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
Top Related Hashnode Post
No results found

We don’t intend to support Node versions that aren’t maintained anymore by Node themselves. Not only to make our life easier, but also because some of our dependencies do that too, and need to be kept updated (thus making such Node requirements a necessity).
The default value change for
enableGlobalCacheshould be well documented when yarn 4 is released. This tripped me up when switching since we sync our local cache folder into our docker dev environment and I was confused why docker didn’t work anymore. I expect this might happen to a few other people.