Yarn

Fast, reliable, and secure dependency management - @arcanis handles this account

[Yarn @yarnpkg]

It’s happening. Yarn 6 Preview is here 💫

Yes, we rewrote it in Rust 🦀⚡️

I'm incredibly excited for the future of our beloved package manager. See the benchmarks and plans in our latest post: https://t.co/7AvujMya97

[Yarn @yarnpkg]

@kdy1dev Interesting!

I had explored using ld_preload or fuse a long time ago, but was concerned about shipping native binaries (at the time Yarn was a single-js-file-distribution), and portability was challenging.

But it was a long time ago, glad to see it became a viable approach!

[Yarn @yarnpkg]

They did! We're now working hard to implement the relevant capabilities to let you enable staged publishing; that should come with the incoming 4.16 release 🥳 https://t.co/06sJrR0O4Q

[Yarn @yarnpkg]

The right fixes would likely be for the npm registry to *finally* add support for 2FA publishing in a way compatible with both automations and monorepos. They announced some interest couple of months ago, but it hasn't transformed so far.

[Yarn @yarnpkg]

We just released the 4.15 branch 🎊

One important change is that npmMinimalAgeGate will now default to 1d for new projects.

[Yarn @yarnpkg]

@indy_singh_uk @ramimacisabird `approvedGitDependencies`: https://t.co/8VKQ482kiO

[Yarn @yarnpkg]

The new Yarn website lets you diff packages between versions. No particular reason for that 😅 https://t.co/bmlSjknRyi

[Yarn @yarnpkg]

Literally unplayable

[Valery Melou @valerymelou]

Claude not being able to see that my package manager is Yarn and keep trying npm install is unforgivable 😒

[Yarn @yarnpkg]

@kossnocorp @pnpm Build scripts are already disabled by default in Yarn (and pnpm), and should be enabled on a case-by-case basis in your configuration.

[Yarn @yarnpkg]

The right fixes would likely be for the npm registry to *finally* add support for 2FA publishing in a way compatible with both automations and monorepos. They announced some interest couple of months ago, but it hasn't transformed so far.

[Yarn @yarnpkg]

Reminder that Yarn lets you filter out freshly published packages with `npmMinimalAgeGate` - it's a good idea to use it on your work repos!

[Yarn @yarnpkg]

Unfortunately it can't help people that happen to create new projects right when the vulnerability is up, since they rarely configure that in their home folder. And making it a default could impair security fixes (for instance the Next.js/React CVEs).

[Yarn @yarnpkg]

@cadamsdev @bunjavascript It doesn't segfault

[Yarn @yarnpkg]

It’s happening. Yarn 6 Preview is here 💫

Yes, we rewrote it in Rust 🦀⚡️

I'm incredibly excited for the future of our beloved package manager. See the benchmarks and plans in our latest post: https://t.co/7AvujMya97

[Yarn @yarnpkg]

Our team is looking for a contractor to help us reimplement the Yarn website using @docusaurus 🧶 If interested, please send us a DM with references!

[Maël @arcanis]

Introducing Yarn 3.1! 🎃👻 Corepack, ESM, pnpm mode, Optional Packages ... https://t.co/ez8IoSbRKk

[Maël @arcanis]

Hello to Yarn 3! 🚀🤖 Improved performances, exports field, improved patches, esbuild, and more! And a look into what's coming next 😃 https://t.co/vVHrDUHawk

[Yarn @yarnpkg]

@sseraphini The intent is to provide a smoother migration for existing codebases while still advocating soundness as a default for new projects.

[Yarn @yarnpkg]

@sseraphini It won't be "the default". It'll be set by default *for projects migrating from v1*. New projects will still use PnP, no plans to change that.

[Maël @arcanis]

No RFC yet, but it's on our roadmap - perhaps for 3.1. Current syntax I have in mind: https://t.co/GimhbQEJoN

[Maël @arcanis]

Just published Yarn 3.0.0-rc.1! We'll let it bake a few weeks before marking it stable, but it you can already try it now ⭐ Full changelog: 📜
https://t.co/ZwyScOdLAh

[Yarn @yarnpkg]

@ZergyGaming No - our install instructions recommend using the `yarn set version` command, and store the binary within your repository.