ts-monorepo
lerna
Our great sponsors
ts-monorepo | lerna | |
---|---|---|
14 | 162 | |
1,420 | 35,365 | |
- | 0.4% | |
8.6 | 8.9 | |
10 days ago | 19 days ago | |
TypeScript | TypeScript | |
MIT License | MIT License |
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.
ts-monorepo
-
[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?
lerna
-
Add Step-up Authentication Using Angular and NestJS
Open the project up in your favorite IDE. Let's take a quick look at the project organization. The project has an Angular frontend and NestJS API backend housed in a Lerna monorepo. If you are curious about how to recreate the project, check out the repo's README file. I'll include all the npx commands, CLI commands, and the manual steps used to create the project.
-
Things I learned while building projects with NX
Lerna currently maintained by Nx team
- tsParticles 3.0.0 is out. Breaking changes ahead.
-
Nx 16.8 Release!!!
On Netlify's enterprise tier, approximately 46% of builds are monorepos, with the majority leveraging Nx and Lerna. Recognizing this trend, Netlify has focused on enhancing the setup and deployment experiences for monorepo projects. In particular they worked on an "automatic monorepo detection" feature. When you connect your project to GitHub, Netlify automatically detects if it's part of a monorepo, reads the relevant settings, and pre-configures your project. This eliminates the need for manual setup. This feature also extends to local development via the Netlify CLI.
- Mocha/Chai with TypeScript (2023 update)
-
Help with library implementation in a big webapp
This is the exact problem monorepos were born to solve. Not only will a monorepo let you share UI components, you'll be able to gradually add shared application logic as well (for instance, do all of your apps have their own logic for connecting to a database? you could roll that into a shared library with a monorepo). There are a lot of tools for accomplishing this in JS, but probably the most popular is lerna, which is built on top of NX (though lots of teams roll their own monorepo in nx without lerna, which IMO is a totally valid option).
-
How to Build and Publish Your First React NPM Package
To begin, you need to prepare your environment. A few ways to build a React package include tools like Bit, Storybook, Lerna, and TSDX. However, for this tutorial, you will use a zero-configuration bundler for tiny modules called Microbundle.
-
Utility for making sure that I'm using the right `@types/react`
If so, are you using a monorepo tool like Nx or Lerna? If not, start there and see if it solves your problem.
-
[AskJS] Is there a silver bullet for consuming Typescript libraries in a Monorepo?
I mean I don't know what your monorepo looks like, but for example infernojs (actually written with typescript) uses lerna, and lerna seems simpler than typescript references
-
Understanding npm Versioning
Tools for publishing, such as Lerna (when using the --conventional-commit flag), follow this convention when incrementing package versions and generating changelog files.
What are some alternatives?
tsconfig-paths - Load node modules according to tsconfig paths, in run-time or via API.
turborepo - Incremental bundler and build system optimized for JavaScript and TypeScript, written in Rust – including Turborepo and Turbopack. [Moved to: https://github.com/vercel/turbo]
babel-plugin-tsconfig-paths-module-resolver - Use tsconfig-paths in any bundler that supports a custom babel config.
nx - Smart Monorepos · Fast CI
typescript-rollup - A Single-Page Application(SPA) built using TypeScript, Rollup.js, and Web Dev Server
changesets - 🦋 A way to manage your versioning and changelogs with a focus on monorepos
alias-hq - The end-to-end solution for configuring, refactoring, maintaining and using path aliases
pnpm - Fast, disk space efficient package manager
lerna-lite - Subset of Lerna in a smaller & more modular project. Helps manage and publish multiple packages in a monorepo/workspace structure
webpack - A bundler for javascript and friends. Packs many modules into a few bundled assets. Code Splitting allows for loading parts of the application on demand. Through "loaders", modules can be CommonJs, AMD, ES6 modules, CSS, Images, JSON, Coffeescript, LESS, ... and your custom stuff.
nestjs-monorepo-microservices-proxy - Example of how to implement a Nestjs monorepo with no shared folder
single-spa - The router for easy microfrontends