ng-packagr
lerna
ng-packagr | lerna | |
---|---|---|
6 | 162 | |
1,836 | 35,408 | |
-0.1% | 0.3% | |
9.3 | 8.9 | |
10 days ago | 5 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.
ng-packagr
-
Adding scss assets to Angular library
Let’s add this folder, and all files in it, to the ng-package.json file of the library. You can find more information here about why we should declare this assets property.
- Are Secondary Entry Points for Libraries still a Good Idea?
-
How to split an Angular app into micro-frontend apps
Additionally, to create a new library for each piece you want to share, you could use the Secondary entrypoints feature of ng-packagr to group common things together, like components or services, and group them together by a more specific feature. But consider this will requires additional updates to the configuration.
-
Overview over Angular’s repositories
ng-packagr repo (link)
-
How to update a NodeJS TypeScript library for ESM-compliance?
Specifically for Angular, we have the Angular Package Format, which is produced by the CLI or by the standalone ng-packagr tool.
-
Relative import from lib's secondary entry point ❌ Error TS5055: Cannot write file X.d.ts because it would overwrite input file
ng-packgr will build the entry points in the following order:
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?
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.
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]
angular-cli - CLI tool for Angular
nx - Smart Monorepos · Fast CI
tsup - The simplest and fastest way to bundle your TypeScript libraries.
changesets - 🦋 A way to manage your versioning and changelogs with a focus on monorepos
ng-builders - Custom Angular CLI builders
pnpm - Fast, disk space efficient package manager
ngx-nrwl-airlines-workspace - Nrwl Airlines workspace using Angular CLI
ngx-unused-css - Angular unused css detection
single-spa - The router for easy microfrontends