Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Angular 8 / Ivy / Other Ideas

See original GitHub issue

Type of Issue

[ ] Bug Report
[ ] Feature Request

Description

To discuss:

breaking changes in compiler API?
expected changes in compiler output

How To Reproduce

tbd

Expected Behaviour

tbd

Version Information

$ node_modules/.bin/ng-packagr --version
ng-packagr: 4.5.x

Issue Analytics

State:
Created 5 years ago
Comments:15 (11 by maintainers)

Top GitHub Comments

1reaction

JoostKcommented, Sep 12, 2019

AFAIK, the packaging of a library will still be following APF spec for Ivy eventually, it’s more of emitted private APIs emitted in the JS that might be updated/change on minors which might not be backwards/forward compatible.

Note that this is only true for the time being, the plan is definitely to have a stable instructions API so packages can ship Ivy code to NPM. Since there’s still some tweaking going on to the instructions, they are not considered stable yet.

1reaction

alan-agius4commented, Jun 19, 2019

Hi @mnahkies, as of now there is not yet a clear workflow on how Ivy libraries should be packaged, it can be a matter of just setting enableIvy to true.

The current recommended way is to ship VE libraries were users that want to use them with Ivy will need to transform them with NGCC, which is done transparently for the users that are using the Angular CLI.