-
Notifications
You must be signed in to change notification settings - Fork 433
Milestone for Angular 5 #516
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
Comments
Sure! So Angular 5 was setup, but then there were some big production issues I didn't realize we'd face, some of the issues included:
Lastly the most important one is:
It might be better for us to move towards that regardless, as it'll solve the above issues (since AngularCompilerPlugin for example was built with the CLI in mind, etc). A lot to think about :) |
Waiting on ngtools/webpack PR to get merged and published here and this should allow us to upgrade back to Angular 5.x |
Good news:) can't wait... Christmas is comming :))
…On 20 Dec 2017 22:17, "Mark Pieszak" ***@***.***> wrote:
Waiting on ngtools/webpack PR to get merged and published here and this
should allow us to upgrade back to Angular 5.x
angular/angular-cli#8951
<angular/angular-cli#8951>
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#516 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ALwXD06NPGSopJ3nYBVwvp1t3zmrzwo3ks5tCYeXgaJpZM4RAbfl>
.
|
Oh man, moving to angular client is going to be fun. Does that mean we will be getting rid of webpack? Cause... I JUST finally got my head wrapped around how the hell that works! lol. |
@MarkPieszak Will updating to Angular 5 fix the issue of not being able to have DOM elements be used in our code? |
No you'll still not be able to use browser only APIs like Yes, the CLI will make life a lot easier! |
Awesome, I'm trying to get https://github.com/swimlane/ngx-charts to work, and I just found out that their branch for updating to ng5, has the fix I'm gunna need, probably. |
Any ETA for those production issues? |
@MarkPieszak they merge mentioned PR 🥇 . Our team needs to push code to production, urgently. how could we make a hot fix for aot bugs? |
I simply disabled AOT to don't lose SSR. It appears that we have to make a choice here, between AOT or SSR. :/ I think we should just track #482 and try to find a solution for that. |
I thought the fix from angular teams (angular/angular-cli#8951) should allow compiling the AOT. Just general off topic l info, I disabled both SSR and AOT, and the system works on Azure with all kestrel goodies, so the pages loading in 800ms due to cache. The SSR and AOT will cut the script rendering times,which will reduce total loading times from 2sec to just 1..which is faster then Amazon (our system have more then 100 components :)) ) |
I'm trying to discover if it was really fixed, but I got no responses. |
The 5.0 version is fixed, I'm now merging the PR #538 into Master. It's not totally perfect, but Production builds are finally possible. Hopefully in a few weeks I'll have the transition to the CLI-based template in there, and we'll be in even better shape 👍 Closing for #539 |
Hi
First of all, thank you for your effort bringing angular universal to .core ecosystem.
Could you please add a milestone for angular 5 migration? It will be easier to watch the progress of migration to angular 5...
Or at least, please provide a list of issues which should be closed before migration to angular 5 could happen.
Thank you
The text was updated successfully, but these errors were encountered: