You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Bundled metadata does not reflect metadata lowering. #21082
Note that the new expression the the metadata for SelectableListModule which not present in src/app/selectable-list/directive/selectable-list/selectable-list.directive.metadata.json when compiled with ngc -p ./src/tsconfig.app.json.
What is the motivation / use case for changing the behavior?
In the repro at https://github.com/georgiee/ng-packagr-foos, the bundled metadata json (scoped-some-name.metadata.json) has no metadata for FooModule and FooComponent. But, these two are exported by the FESM bundles ((esm5|esm2015)/scoped-some-name.js).
This is a longstanding and well known issue with View Engine's metadata bundler, and is systemic and non-trivial to fix. The good news is that Angular Ivy does not use the metadata system at all, and therefore this bug is rapidly becoming obsolete.
Activity
dherges commentedon Jan 25, 2018
Here is another issue description:
Is that the same issue?
alxhub commentedon May 28, 2020
This is a longstanding and well known issue with View Engine's metadata bundler, and is systemic and non-trivial to fix. The good news is that Angular Ivy does not use the metadata system at all, and therefore this bug is rapidly becoming obsolete.
JoostK commentedon May 14, 2021
With v12 now allowing libraries to be compiled with the Ivy compiler, this issue has been resolved.
angular-automatic-lock-bot commentedon Jun 14, 2021
This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
This action has been performed automatically by a bot.