berry

Deterministic to a fault unless you mix Windows and Linux. https://github.com/yarnpkg/berry/issues/6105

It’s on by default in yarn 4 too now, but pnpm was the first to market that default minimum gate. https://github.com/yarnpkg/berry/pull/7135

yarn pnp is currently broken on Node v25.7+; - https://github.com/yarnpkg/berry/issues/7065 - https://github.com/nodejs/node/issues/62012 This is because yarn patches fs in order to introduce virtual file path resolution of modules in the yarn cache (which are zips), which is quite brittle and was broken by a seemingly unrelated change in 25.7. The discussion in issue 62012 is notable - it was suggested yarn just wait for vfs to land. This is interesting to me in two ways: firstly, the node team seems quite happy for non-trivial amounts of the ecosystem to just be broken, and suggests relying on what I'm assuming will be an experimental API when it does land; secondly, it implies a lot of confidence that this feature will land before LTS.

HN sanitizes line anchor, so here’s the link: https://github.com/yarnpkg/berry/blob/a592371321068c3d63b093...

Pnpm has a new setting to stave off supply chain attacks https://news.ycombinator.com/item?id=45286526 yarn feat: implement npmMinimumReleaseAge and npmMinimumReleaseAgeExclude config options https://github.com/yarnpkg/berry/pull/6901

Yarn just landed a similar feature too https://github.com/yarnpkg/berry/pull/6901

Location: London, UK Remote: Yes Willing to relocate: No Technologies: Programming Languages: Java, C++, Ruby, JavaScript, TypeScript Web Technologies: HTML, CSS, ReactJS, NextJS, Electron, CSS in JS Mobile Development: React Native Back-end Technologies: NodeJS, RESTful APIs, GraphQL APIs, Database Management Database Technologies: PostgreSQL, Prisma, Postgres Résumé/CV: https://juresotosek.com/CV-JureSotosek.pdf Email: jure.sotosek@gmail.com Hi, I'm both a founder of a successful micro-startup and a Frontend leaning Full-stack Software Engineer looking for a new challenge. Highlights of my career: WrumerSound: I founded, developed, and scaled an e-commerce business around Wrumer, a device and app that simulates engine sounds through car speakers. Wrumer has achieved approximately €30k in monthly sales, tra

I think Prolog really shines as an embedded query engine (I know this is old and it's been removed since). It's perfect for declarative configuration, very easy to write powerful queries once you wrap your head around it. The Yarn constraints plugin also used (Tau) Prolog, although it looks like it's in the process of being replaced with JS, which makes me a bit sad. The reasoning is here: https://github.com/yarnpkg/berry/issues/1276. Seems like the biggest issue is lack of a nice dev environment. I maintain the Trealla Prolog Wasm port (npm package 'trealla') and I hope some day to use it for a VSCode extension or LSP or something to provide a nice dev experience. Tau's performance has also been cited as an issue[1] but Trealla is quite fast and I expect it could easily handle a complex Yarn workspace with tons of facts. If this sounds l

I have just discovered yarn2 / yarn3. The main advantage over npm / pnpm seems be the Zero Install philosophy [1] and the Plug'n'Play architecture [2]. Have you some feedback about these features? By the way, the yarn2 / yarn3 project is hosted on a distinct repository [3]. [1] https://yarnpkg.com/features/zero-installs [2] https://yarnpkg.com/features/pnp [3] https://github.com/yarnpkg/berry

Summarizing the 3 major JS package management approaches: * Classic node_modules: Dependencies of dependencies that can't be satisfied by a shared hoisted version are nested as true copies (OSes may apply copy-on-write semantics on top of this, but from FS perspective, these are real files). Uses standard Node.js node_modules resolution [1]. * pnpm: ~1 real copy of each dependency version, and packages use symlinks in node_modules to point to their deps. Also uses standard resolution. Requires some compatibility work for packages that wrongly refer to transitive dependencies or to peer dependencies. * pnp[2]: 1 real copy of each dependency version, but it's a zip file with Node.js and related ecosystem packages patched to read from zips and traverse dependency edges using a sort of import map. In addition to the compatibility work require

That repo is for Yarn v1. V2 (now v3 ...) lives at https://github.com/yarnpkg/berry. No idea why they did it that way. Probably because Yarn 1 is still very actively used, and things would get confusing otherwise.

From the looks of it, the Yarn "team" is mostly one guy. Edit: I retract my previous comment, the additions/deletions count seems misleading. [1] https://github.com/yarnpkg/berry/graphs/contributors

Hmm. Okay, digging around in the Yarn repo, I see this "generate patch" setup code [0]. Looks like they're trying to cherry-pick some specific commits from the TS repo based on the TS version, and specifically apply them to the TS file. The "base64" bit is referenced here [1]. I would assume this specifically relates to the fact that TS does not have native support for Yarn PnP as a filesystem approach. The Yarn team has been keeping an open PR against TS [2] and trying to convince the TS maintainers to merge it, but it hasn't happened yet. A bit odd, and I can understand why you're concerned, but it also looks like there's a very understandable reason for this. I would have assumed that this doesn't get applied if you install TypeScript via the Yarn v2 `node_modules` linker, but would have to try it out and actually see. [0] https://g