ng-packagr VS angular-cli

For an extended period, tree shaking with Angular libraries is supported when using secondary-entrypoints, which is supported by ng-packagr.

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.

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.

ng-packagr repo (link)

Specifically for Angular, we have the Angular Package Format, which is produced by the CLI or by the standalone ng-packagr tool.

ng-packgr will build the entry points in the following order:

[x] https://github.com/angular/angular-cli/pull/28405 / https://github.com/angular/angular/issues/58123

This project was generated using Angular CLI version 19.0.7.

Shame on me, I didn't know that Node.js can't load modules via HTTP. So I had to find a workaround. Node.js supports hooks for loading modules, and this is already at the release candidate stage. Angular 19 even uses this method to generate the manifest file. Wrote an quick and dirty code which worked. Created an issue, suggested a pull request with POC, but there was no response. What's left? Make your own solution.

There are open PRs for Karma and Jest Experimental Builder to support AOT.

module.exports = async (util, rule, host, injector) => { let list = await util.changeList([ { type: 'copy', source: 'git', from: { url: 'https://github.com/angular/angular-cli.git', match: '/packages/schematics/angular/directive/files', output: '/packages/schematics/angular/directive/files', }, pathTemplate: '@angular-devkit', contentTemplate: '@angular-devkit', pathTemplateSuffix: '.template', templateContext: { name: 'hello', standalone: true, selector: 'hello', 'if-flat': (input) => '' }, to: './hello-directive' }, ]); await util.updateChangeList(list); };

Well, scream though I have, the Angular team desperately needs to Remove NodeJS Dependencies, as it has already fallen behind from all frameworks concerning deployment. I'm still waiting for the response on this... 🦗 🦗 🦗 🦗

PR: feat(@angular-devkit/build-angular): add define build option to application builder

The new ssr CommonEngine source code

Source: https://github.com/angular/angular-cli/issues/25134

I'm not sure how to solve this but here's something that looks similar to your issue - https://github.com/angular/angular-cli/issues/24373