-
Notifications
You must be signed in to change notification settings - Fork 841
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(angular): rename projects for better report readability #845
Conversation
I'm planning to remove the angular 8 implementations, since we should focus on the current version. Sadly so far I failed to create an angular 11 closure build. Do you have any pointers or can you contribute such an implementation (the regular "angular-closure" one would suffice) ? |
I will migrate two closure projects to ng11, hopefully in a few days. Sorry for the late reply. I hope it's ok to make it part of this PR |
That sounds great! |
a98335c
to
68cb3c8
Compare
Thanks, but the closure builds do not work properly on my machine. Can you please take a look at it?
|
Can you tell me what OS and node version you use? |
The error happens on Fedora 33 (on my notebook, both with node 14.13.0 and node 15.7.0) and in the docker container with an Ubuntu 20.10 (node 14.4.0). |
The problem is with Closure The support for the Closure compiler in Angular packages has been broken for quite some time. As of TS3.9 Closure is unusable with the JavaScript emit. Please follow microsoft/TypeScript#38374 for further developments. Meanwhile, I have switched to using |
This PR consists of the following changes:
google closure compiler
androllup
for devangular-{closure}-{nozone}
PlatformBrowserDynamic
replaced withPlaformBrowser
as there are no dynamic components