angular-cli VS ng-packagr

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

Sass errors after migrating from Angular 13 to 15 / Node 14 to 18

Edit: Found it at Github https://github.com/angular/angular-cli/issues/25574. So it seems to be a problem

Remove Dependencies for NodeJs

Is it possible to teach llm to read issues and answer questions such as how do I get angular 17 to output to dist instead of dist/browser with you can't do this with angular. However, in your CI CD pipeline, you can do a mv or robocopy or bla bla bla depending on context?

https://github.com/angular/angular-cli/issues/26028

It would be very useful because there are so many edge cases that aren't covered in the docs but are probably available in some kind of WON'T FIX issues.

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: