ts-monorepo VS monorepo-template

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.

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.

Give https://github.com/NiGhTTraX/ts-monorepo a try :) It uses path aliases to map your imports to the source code inside the monorepo.

Make sure you've copied the jest craco config and that you've set up path aliases accordingly.

You can check https://github.com/NiGhTTraX/ts-monorepo.

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).

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.

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.

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

I built this monorepo template around Yarn, and I base all my projects on it now.

I just pushed something similar to this recently: https://github.com/monorepo-template/monorepo-template . Though it doesn't have everything you seek, it may offer a solid foundation to build from.

Just for this, I wrote an intricate coverage report system that operates in the preconfigured CI. The applications run both a Jest and Cypress test suite, then the coverage reports for those suites are merged: and 100% coverage is enforced from there. You can see this in action in the example application, where the end-to-end tests cover all code paths except mounting to the root node, which should never fail in production and therefore cannot be tested on a live application. The e2e coverage report will show all files except that one covered, and the unit test report will show only that one covered, but the combined report, which enforces 100% coverage, will show that all paths were covered. Example pipeline

The monorepo template is a GitHub repository template that preconfigures common front end dependencies for best practices and abstracts them in an extensible manner.

Open source repository in question and its license file