orogene VS wireit

Interesting, but no support for workspaces yet: https://github.com/orogene/orogene/issues/161

Yarn is actually slower than npm these days. Here's some current benchmarks:

https://github.com/orogene/orogene/blob/main/BENCHMARKS.md

In short, Kat left npm at some point in 2019 after a whole debacle with leadership. For a while they were working on orogene with a couple other ex-npm people, but nothing came out of that. It's really a shame because it looked really promising and they had a lot of cool ideas.

npm workspaces plus Wireit works far better than Lerna, in my experience.

https://github.com/google/wireit

Wireit's ability to specify actual script dependencies, do caching (and on Github actions), and it's long-running service script support make it much more useful and comprehensive than Lerna.

I agree that this should be built into npm. There's an RRFC for it here: https://github.com/npm/rfcs/issues/706

I must admit I'm a bigger fan of the wireit[0] approach, the only pause I have is its a Google project, my temptation is to fork it. The code isn't terribly complex

My biggest complaint with NX is: lack of a sane API for plugins, and it has more overhead than I'd care for. For the amount of complexity that NX has, I'd rather use Rush[1] which gives you everything NX does. My only complaint with Rush is that its development is really slow going, they really need to focus up on Rush plugins (they're good, but still experimental, and I'd love to see them clean up how `autoinstalls` work to be more intutive)

I'm on the fence about turbo from Vercel

[0]: https://github.com/google/wireit

[1]: https://rushjs.io/

To further derail the conversation there's also https://github.com/google/wireit

There's also wireit made by Google which pairs well with Yarn/NPM workspaces

Google recently anounced wireit, a program that runs multiple NPM scripts that depend on one another. Combined with NPM Workspaces, it enables monorepo workflows that previously required tools like Yarn and Pnpm.

etc.

where a bunch of related projects live top-level in a repo. Each project has a packages folder that includes the core implementation, as well as demos, framework-specific adaptors, etc.

In each package's package.json, I have a series of commands (convert the TS to JS, make a bundle, deploy to Firebase, etc.). Each command can depend on another, either in the same project or anywhere else in the file hierarchy.

This provides two benefits:

1. Iterating across packages is faster, because I don't have to worry about making sure each package rebuilds in the right order if I make a change in a library.

2. Filesystem concerns are separated: rollup only needs to worry about bundling, and it only needs to bundle web-facing projects. The only tool my libraries need is tsc.

(Using TypeScript and Rollup together is kind of a pain in the ass because you have to fiddle with picking the right TS plugin and configuring it. This is also often the long pole on doing a Rollup version upgrade. Decoupling the two makes Rollup way simpler/easier/nicer to use, which makes wireit awesome even if you don't have multiple packages.)

Here's a snippet from one of my package.jsons. They basically all look like this. (start is complicated because of https://github.com/google/wireit/issues/33. When that's resolved, it will be as simple as the others.)

    "scripts": {