How to process @angular packages with the linker without @angular/cli

Which @angular/* package(s) are relevant/releated to the feature request?

compiler-cli

Description

Before 13.0.0.-next.10 it was possible to execute ngcc and let it process the @angular/* packages to get ivy output in full compilation mode.

With the current release, 13.0.0-next.11, the exeuction of ngcc does not process the @angular/* packages. Therefore, these packages remain in partially compilated outputs and can’t be used directly in the browser.

Running ngcc:

Browser error:

Imports packages:

Proposed solution

It would be great to have some sort of tooling / option to process the @angular/* packages with the linker without having to use the @angular/cli.

Alternatives considered

One alternative would be to also publish the @angular/* packages in fully compilated mode.

cheers flash ⚡

[petebacondarwin]

@flash-me - I just realised, given your low bundler tooling approach, that you should be aware that the new Angular Package Format (APF) for v13 will default to ES2020, which is not compatible out-of-the-box with Zone.js if the library uses the async await syntax.

There are a couple of options:

• only use libraries that do not use async - await functions.
• apply a transform (e.g. Babel 😱 ) to downlevel the ES2020 to ES2015 (or at least downlevel the async-await syntaxes).
• configure your import-maps to point at the special FESM2015 export in the new format. (Is that possible?)

---

EDIT: sorry I made a mistake - the default is still ES2015 (see @angular/core@next):

"module": "./fesm2015/core.mjs",

So this should not be a problem.

[flash-me]

Conceivably, you could build your own AST manipulation library and then implement the AstHost interface, allowing you to completely drop Babel (and TypeScript) from the transformation. But do you really want to have to maintain that?

TBH: Probably not 😄 It’s just the step away from just using ngcc to introducing another dependency to get things work. But since my approach is not the casual use case of the majority, I’m aware that I might have to solve some stuff on my own.

But as I said, the use of @babel/cli is acceptable for me.

cheers flash ⚡