-
-
Notifications
You must be signed in to change notification settings - Fork 4.9k
No Upgrage to NG6 ? #2012
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
@gaojinbo010 Please check branch migrate-to-webpack4 . which is angular 6 added |
Can you please share any release schedule, feels like this repo has come to a stall when it comes to keeping up with dependent package versions. |
@WillooWisp I don't know when will master branch be updated. but We have branch with latest version packages. |
Hello, currently I'm using Angular 4.4 created using this Starter. Would I have to look up the changes for previous versions and do it manually? Thank you in advance for you comments and huge thank you for maintainers of this repo :) |
@aledpardo I think easy would be to close our angular 6 branch and put you code inside source folder. I think that will be easy if you have not customize our webpack files....... |
@govi2010 thanks for quick reply. I'll try this approach, but I'm sure my webpack files were customized a bit. |
Are there any known issues with feature/migrate-to-webpack4 branch? If not, we can create a pull request into master. |
After 2 weeks of testing in our project, didn't find any significant issues, so the branch was merged into master. |
Note: for support questions, please use one of these channels: Chat: AngularClass.slack or Twitter: @TipeIO
I'm submitting a ...
[ ] bug report
[ ] feature request
[ ] question about the decisions made in the repository
Do you want to request a feature or report a bug?
What is the current behavior?
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem via
https://plnkr.co or similar (you can use this template as a starting point: http://plnkr.co/edit/tpl:AvJOMERrnz94ekVua0u5).
What is the expected behavior?
What is the motivation / use case for changing the behavior?
Please tell us about your environment:
The text was updated successfully, but these errors were encountered: