lerna-lite
Subset of Lerna in a smaller & more modular project. Help manage and publish multiple packages in a monorepo/workspace structure (by lerna-lite)
ts-monorepo
Template for setting up a TypeScript monorepo (by NiGhTTraX)
| lerna-lite | ts-monorepo | |
|---|---|---|
| 2 | 14 | |
| 561 | 1,620 | |
| 0.4% | 0.0% | |
| 9.6 | 9.3 | |
| 9 days ago | 7 days ago | |
| TypeScript | TypeScript | |
| MIT License | MIT License |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
lerna-lite
Posts with mentions or reviews of lerna-lite.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2025-09-29.
-
OIDC Trusted Publishing with Lerna-Lite
Lerna-Lite is a lighter version of Lerna (every commands are optional in Lerna-Lite) as opposed to Lerna which is a "all-in-one" tool. Another difference is that the newest Lerna version has Nx as a dependency, but on the other hand Lerna-Lite does not require neither use Nx.
-
Lerna has gone. Which Monorepo is right for a Node.js BACKEND now?
I've just switched over to lerna-lite since I just need lerna's versioning and run support.
ts-monorepo
Posts with mentions or reviews of ts-monorepo.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-05-09.
-
[AskJS] Is there a silver bullet for consuming Typescript libraries in a Monorepo?
1. Linking libs with tsconfig paths. This approach involves setting a tsconfig.json paths object which maps the package name, to the local filesystem location. Eg. "paths": {"@org/lib":"../libs/lib"} - Nx uses this approach for their Integrated Monorepo configuration https://nx.dev/tutorials/integrated-repo-tutorial https://github.com/NiGhTTraX/ts-monorepo.
-
Recommendations for lerna/yarn mono repos?
FYI I tried renaming packages/bar/index.ts to index.js and adding allowJs: true in its tsconfig.json and tsconfig.build.json and everything works as expected.
-
Structuring packages and working with workspaces
Give https://github.com/NiGhTTraX/ts-monorepo a try :) It uses path aliases to map your imports to the source code inside the monorepo.
-
How to use npm workspace with create-react-app and typescript?
Make sure you've copied the jest craco config and that you've set up path aliases accordingly.
-
Handling TypeScript in a monorepo
You can check https://github.com/NiGhTTraX/ts-monorepo.
-
You might not need TypeScript project references
FWIW https://github.com/NiGhTTraX/ts-monorepo works in a similar way by using path aliases instead. The result is the same (imports resolve to monorepo source code), but this approach doesn't prevent you from publishing any of the packages (check the repo and the linked docs for more details).
-
using references in tsconfig.json to point to library code
You didn't give an example of how your imports look, but I'm assuming you're trying to use absolute imports for the lib files like from 'lib/src/...'. Project references don't rewrite the imports in any way, they just optimize the builds by caching referenced projects. You'll want to use path aliases instead. Feel free to check out https://github.com/NiGhTTraX/ts-monorepo for full examples.
-
[Question] Setting up monorepo: How be able to debug and build in the same project without changing package.json?
You can use two tsconfig.json files and in one of them configure path aliases to map your package names to the source code, effectively "overriding" package.json#main. You can find examples here https://github.com/NiGhTTraX/ts-monorepo.
-
Monorepo with Yarn Workspaces + TS + Docker Templates
Here is one I liked that is very basic, although I removed lerna from it personally. Shows examples of package sharing and a bunch of popular libraries. Next not nuxt but you get the idea. https://github.com/NiGhTTraX/ts-monorepo
- How do you manage TypeScript monorepos?
What are some alternatives?
When comparing lerna-lite and ts-monorepo you can also consider the following projects:
typescript-monorepo-example - An example of setting up a Lerna monorepo with Visual Studio Code and TypeScript
babel-plugin-tsconfig-paths-module-resolver - Use tsconfig-paths in any bundler that supports a custom babel config.
pnpm-turborepo-auto-boilerplate - A monorepo boilerplate using pnpm, turborepo, and auto.
tsconfig-paths - Load node modules according to tsconfig paths, in run-time or via API.
syncpack - Consistent dependency versions in large JavaScript Monorepos.
alias-hq - The end-to-end solution for configuring, refactoring, maintaining and using path aliases