cli VS angular-cli

Because sometimes I make idiotic mistakes and I really don't want that embarrassing stuff out there where people can see. I ran head first into an npm bug once when I tried to symlink the README file which resulted in the thing getting published without a README.

https://github.com/npm/cli/issues/6746

Embarrassing. And then they slapped me with a stupid 24 hour count down on top of it. I seriously hate this thing.

This is the same NPM that made a change causing the `integrity` field to go silently missing from `package-lock.json` [0] when installing packages, and then also not complaining at any other time in the future.

[0] https://github.com/npm/cli/issues/4460

Node.js v21 includes npm v10.2.0, which notably introduces a new sbom command that allows you to generate a Software Bill of Materials (SBOM) for the current project. You can read more about the changes in recent NPM releases on GitHub.

npm ERR! This is an error with npm itself. Please report this error at: npm ERR! https://github.com/npm/cli/issues

You'll need an AWS account and AWS credentials configured locally. We'll use pnpm but you could also use npm or yarn. The finished app is available on github.

~/Documents/amplify-hackathon/amplify-react-graphql-demo main !5 ?3  npm install -g @aws-amplify/cli  1 ✘ 4s 22:11:35 changed 26 packages in 25s 7 packages are looking for funding run `npm fund` for details npm notice npm notice New minor version of npm available! 9.4.0 -> 9.6.5 npm notice Changelog: https://github.com/npm/cli/releases/tag/v9.6.5 npm notice Run npm install -g [email protected] to update! npm notice

10 18.95 npm notice Changelog: https://github.com/npm/cli/releases/tag/v9.6.4

npm WARN deprecated [email protected]: See https://github.com/lydell/source-map-resolve#deprecated npm WARN deprecated [email protected]: This SVGO version is no longer supported. Upgrade to v2.x.x. added 1692 packages, and audited 1699 packages in 23s 211 packages are looking for funding run `npm fund` for details 27 vulnerabilities (1 low, 7 moderate, 18 high, 1 critical) To address issues that do not require attention, run: npm audit fix To address all issues (including breaking changes), run: npm audit fix --force Run `npm audit` for details. npm notice npm notice New minor version of npm available! 9.5.1 -> 9.6.2 npm notice Changelog: https://github.com/npm/cli/releases/tag/v9.6.2 npm notice Run npm install -g [email protected] to update! npm notice

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.