Skip to content

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

Closed
mcgri opened this issue Dec 13, 2017 · 13 comments
Closed

Milestone for Angular 5 #516

mcgri opened this issue Dec 13, 2017 · 13 comments

Comments

@mcgri
Copy link

mcgri commented Dec 13, 2017

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

@MarkPieszak
Copy link
Member

MarkPieszak commented Dec 14, 2017

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:

  • Move to Angular-CLI based template

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 :)

@MarkPieszak
Copy link
Member

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

@mcgri
Copy link
Author

mcgri commented Dec 20, 2017 via email

@Adondriel
Copy link
Contributor

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.

@Adondriel
Copy link
Contributor

@MarkPieszak Will updating to Angular 5 fix the issue of not being able to have DOM elements be used in our code?

@MarkPieszak
Copy link
Member

MarkPieszak commented Dec 21, 2017

No you'll still not be able to use browser only APIs like document.querySelector / navigator or anything window, but you'll have access to DOCUMENT from common which is a server implementation of the Document, so if you use that, you can do querySelectors for example. But typically if you're trying to query things, there's probably a better more Angular way of doing it, so try to avoid that :)

Yes, the CLI will make life a lot easier!

@Adondriel
Copy link
Contributor

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.

@Adondriel Adondriel added this to the Update To Angular 5 milestone Dec 22, 2017
@jerkovicl
Copy link

Any ETA for those production issues?

@mcgri
Copy link
Author

mcgri commented Jan 9, 2018

@MarkPieszak they merge mentioned PR 🥇 . Our team needs to push code to production, urgently. how could we make a hot fix for aot bugs?

@odahcam
Copy link
Contributor

odahcam commented Jan 22, 2018

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.

@mcgri
Copy link
Author

mcgri commented Jan 22, 2018

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 :)) )

@odahcam
Copy link
Contributor

odahcam commented Jan 23, 2018

I'm trying to discover if it was really fixed, but I got no responses.

@MarkPieszak
Copy link
Member

MarkPieszak commented Jan 23, 2018

The 5.0 version is fixed, I'm now merging the PR #538 into Master.
Take a look and let me know!

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants