wireit

re 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. (Before wireit, using TypeScript and Rollup together was a pain in the ass because you'd have to fiddle with picking the right TS plugin and configuring it. This was 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.) It's also a good replacement for lerna. Each of my packages has a publish command that runs `gitpkg publish`. My root package.json has a publish command that depends on all the packages' publish commands. Thus, I can run `yarn run publish` in the root of my monorepo and trust that all of my packages have been published to our git host appropriately. (gitpkg lets you turn a git host into a private registry, so you can share modules without setting up an NPM registry.) 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": { "start": "yarn run -TB concurrently \"yarn run build:tsc --watch\" \"rollup --config ./rollup.config.js --watch\" \"dhost site --bind-all\"", "build": "yarn run -TB wireit", "build:tsc": "yarn run -TB wireit", "build:bundle": "yarn run -TB wireit", "deploy": "yarn run -TB wireit" }, "wireit": { "build": { "dependencies": [ "build:tsc", "build:bundle" ] }, "build:tsc": { "command": "tsc --build --pretty", "clean": "if-file-deleted", "files": [ "src/**/*.{ts,tsx}", "tsconfig.json", "../../tsconfig.common.json" ], "output": [ "dist/**", ".tsbuildinfo" ], "packageLocks": [ "yarn.lock" ], "dependencies": [ "../core:build", "../preact:build" ] }, "build:bundle": { "command": "rollup --config ./rollup.config.js", "clean": true, "files": [ "dist/**/*.js", "rollup.config.js" ], "output": [ "site/mount.js", ".tsbuildinfo" ], "packageLocks": [ "yarn.lock" ], "dependencies": [ "build:tsc" ] }, "deploy": { "command": "firebase deploy", "dependencies": [ "build:bundle" ] } },

it is to maintain (updates etc) - Extensibility: how extensible is it? more importantly, how easily can it be extended? - Built in watch mode that understands its dependency graph for each task, and can run them simultaneously - Works with pnpm / npm workspaces natively - Stream based output: e.g. if running multiple tasks it interleaves them appropriately, even better if they're labeled and color coded - Dependency graph tracking. IE: if I run build for a package, it understands that it may have dependencies that need to be built first. - Able to run tasks arbitrarily on a "per package" process, potentially Now, after mentioning all that, I realize, by reading the docs, in theory Bazel supports all this and has lots of feature headroom for growing features over time which I like, however, I've read mixed things about it, but not all of the sources I've read so far are "up to date" (some articles about people adopting Bazel are years old now) and I wanted to get a more accurate picture of what is going on here. Alternatively, I'm open minded to looking at a different set of tools For context I've done alot of research and experimentation with the follow: - nx[0] - rush[1] - wireit[2] - turbo[3] We've settled on, for now `wireit` in part because it has a really good watch mode feature that `nx` does not (nx doesn't have a built in watch mode for your task runner, it relies on the plugin / script to handle it, which was really problematic). However, wireit isn't extensible, and I'm not looking to have to manage sub task "phasing" with something like `gulp`. This was an issue with rushjs as well (but rushjs has its own challenges and opinions). While rush is starting to expose a direct `rush-sdk` API, its not really documented and I'm not sure about its stability or best way to go about making rush plugins. They also have a competing task runner called `heft` that I'm not sure about in the light of the `rush-sdk` and its use cases (if someone from the rush team sees this and can clarify about the long term vision and where they're at with it now, I'm all ears) tl;dr: I've tried tons of tools, and Bazel seems to check all the boxes, but I'm afraid the complexity will kill us, since we don't have a dedicated tool engineer to oversee it, it has to malleable enough that we can maintain it bit by bit over time [0]: https://nx.dev/ [1]: https://rushjs.io/ [2]: https://github.com/google/wireit [3]: https://turborepo.org/docs

een related JS libraries. [1] https://github.com/google/wireit