Charles

Yarn’s global installs do not work properly with nvm. Don’t have a link right now but there were several issues on yarn’s repo related to it.

The file is provided purely for IDE usage and as a convenience thereof. The CLI does not otherwise use it. Post-generation formatting is currently at the discretion of the developer.

Please note that 0.12.4 is significantly older than 0.800.1.

This can be partially achieved today with `ng generate component COMPONENT_NAME --standalone -st`. The standalone option does not yet have a shorthand name due to it still being in developer...

Developer Preview APIs currently do not have full tooling support. Additional tooling support for Standalone Components will be added in the 14.x timeframe as the APIs are stabilized.

We are investigating a fix for the issue. However, `emitDecoratorMetadata` should generally be avoided when possible due to it having known design limitations that can lead to temporal dead zone...

This issue stems from the use of a class and namespace with the same name. The use of a static property on the class itself would eliminate the need for...

This is expected behavior. You can read more about the error prone nature of default exports and CommonJS libraries here: https://esbuild.github.io/content-types/#default-interop The `jspdf-autotable` package does have an ESM variant of...

This is actually expected behavior for this configuration. TypeScript has provided more formalization of the behavior for the `paths` option. It includes a section on this specific issue which can...

Either the `font-awesome` package root import or the package's Sass variable `$fa-font-path` will need to be set to allow the fonts to be found. Previously the Sass deep import worked...