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
tsickle is intended to adapt TypeScript output to be valid Closure Compiler input.
One feature required is to downlevel decorators into static fields. We do it in a way that doesn't introduce Temporal Dead Zones.
Angular applications and libraries also downlevel decorators, so it was convenient to depend on the tsickle package for this. However it causes a bunch of support burden on tsickle, eg. angular/tsickle#922
where a language feature isn't used with closure compiler, so tsickle team doesn't plan to fix these.
For Angular apps, we fixed this by porting the downleveling code from tsickle to the webpack loader in angular/angular-cli#14473
We need to do something similar for ng-packagr so that Angular libraries can also be built without a tsickle dependency.
The text was updated successfully, but these errors were encountered:
This issue has been automatically locked due to inactivity. Please file a new issue if you are encountering a similar or related problem. This action has been performed automatically by a bot.
tsickle is intended to adapt TypeScript output to be valid Closure Compiler input.
One feature required is to downlevel decorators into static fields. We do it in a way that doesn't introduce Temporal Dead Zones.
Angular applications and libraries also downlevel decorators, so it was convenient to depend on the tsickle package for this. However it causes a bunch of support burden on tsickle, eg.
angular/tsickle#922
where a language feature isn't used with closure compiler, so tsickle team doesn't plan to fix these.
For Angular apps, we fixed this by porting the downleveling code from tsickle to the webpack loader in
angular/angular-cli#14473
We need to do something similar for ng-packagr so that Angular libraries can also be built without a tsickle dependency.
The text was updated successfully, but these errors were encountered: