Unirepo is an extremely opinionated TypeScript build tool.
Typical monorepo management tools in the Node.js ecosystem provide automation around package maintenance, but still permit and require users to muck around with poly-package configuration. Package boundaries must be manually maintained, each with its own sub-configuration.
Unirepo is different because sub-package configuration is managed centrally and uniformly. Package boundaries are managed automatically via bundling and code splitting.
You will have one and only one list of dependencies. Your package.json files
will be generated from that source configuration. Same for tsconfig.json.
The source configuration file that - believe it or not - allows code comments.
Unirepo is fast because it is ships as a native binary and builds your code using esbuild.
Additionally, Unirepo has a run subcommand that acts as a substitute for
ts-node. The run subcomain also supports a --watch flag, and so acts
as a substitute for node-dev (or ts-node-dev) as well. Sourcemaps
are always enabled.
As mentioned, Unirepo is extremely opinionated. Those opinions will evolve in to documentation, including a a growing list of anti-features.
Want to see it in action? Check out the Demo Video!
Alpha! Don't use this yet.
See the versioning guide and the roadmap.
Only works for targeting Node currently. Targeting Browsers is planned.
go get -u github.com/brandonbloom/uni- Create a
uni.ymlfile with some package entrypoints. - Manually add dependencies to your config file.
- Run
uni deps.
- Use
uni run src/program.tsto execute programs. They must export amainfunction. - Use
uni build some-packageto pre-compile intoout/dist.
Here's the steps to do in your CI flow:
uni build --version $VERSIONto create packages with version numbers.uni packto create packed.tgzfiles.uni publishto automatenpm publish ./path/to/package.tgz.
The patch-package utility is always available.
Functionality similar to check-engine is builtin, but much faster and with caching.