-
Notifications
You must be signed in to change notification settings - Fork 13.5k
bug: ionic 4.7 update bug #18903
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
Thanks for the issue. Did you follow our Angular 8 Migration Guide? https://docs.google.com/document/d/1QOpQeDifPSg6F9WycDLcbQnpqjN96ew-Ap0_CB7CcCQ/edit There is a link in the guide to a known issue in the Angular CLI where the Static Query Migration might not work. Also for the Can you try that and let me know if it resolves your issue? Thanks! |
@liamdebeasi @brandyscarney, It may be worth noting in the changelog that |
@liamdebeais, the migration guide causes so much issue with npm modules folder. Eventually I need to delete the npm module folder and the package json lock file.. reinstall everything. Reinstall again with the dev only command... it’s a lot of hassle and still no luck. A lot of packages has mismatch peers etc. The conference app seems to have some matching libraries but the angular 8 has so many breaking changes compare to 7... the import libraries are different etc... I will stick with angular 7 with 4.7.0 until the next starter black project that has angular 8 in it, and then I will migrate my code to 8... |
Hi @MrBokeh, Ionic 4.7.0 is fully compatible with Angular 8 and should not introduce the issues you are describing. Can you post the steps you are taking to migrate your project to Angular 8? Additionally, if there is an Angular 7 code base you are testing this on, that would also be helpful to see. |
Here are the steps:
Please help! |
Thanks for the follow up. I was able to reproduce the issue. It looks like you got some of your upgrade instructions mixed up. As stated in the instructions, you should only have to run There is a bug where the CLI will attempt to install Angular 8.2.0-next. The workaround for that is: npm install @angular/cli@latest
npx ng update @angular/core It looks like you combined both the regular instructions and the workaround with: npm install @angular/cli@latest
npx ng update @angular/core @angular/cli When following the guide I no longer ran into the issue you are describing. Can you try following the guide again? |
I have tried this alternative method:
These are the breaking changes:
Also some import errors with all these packages:
|
Thanks for the follow up. Please see the Angular 8 Breaking Changes list: https://github.com/angular/angular/blob/master/CHANGELOG.md#breaking-changes.
Upon resolving these issues, does everything work? |
I will come back to you once I get my app working again... every .ts file has a few breaking changes...! |
Ok great! Since it sounds like the original issue is resolved, I am going to close this issue. If you run into new issues, feel free to open a new issue, and we will take a look. Thanks! |
I think the error told me that those packages have no export member which is not right... |
The original issue is the migration guide is not working which is still true... |
Hi there, As I commented previously the migration guide was not followed properly, but upon following the guide the migration worked. Which packages are you getting |
@MrBokeh Our steps provided for updating Angular 8 are there to help guide users, but it is not an all-inclusive guide. There may be potential issues that you run into when updating but those are due to the Angular update or breaking changes that are introduced by Angular. These are not caused by Ionic 4.7.0. I personally ran into issues when updating the conference app and the following steps worked for me: On conference app master, remove
This comment instead: angular/angular-cli#14589 (comment) Had to commit in between each command below because it warned the repo wasn't clean:
On a mac:
Or on PC:
You may want to look at the following site for more detailed steps tailored to your project: https://update.angular.io/ |
@zmoshansky Thanks! We have this added to the release notes here: https://ionicframework.com/docs/release-notes#4.7.0 But I just added the same to the changelog: https://github.com/ionic-team/ionic/blob/master/CHANGELOG.md#470-nitrogen-2019-07-24 |
Still having a tough time with this. Could not find module "@ionic/angular-toolkit" from "/Users/xxx/git/ionicapp". I am not ready to upgrade ionic. Any thoughts? |
I gave up on the migration guide. I migrated the code manually to a blank starter project... |
I also had major issues migrating, so I will continue on the ion / angular version 4.6.2 |
Thanks for the issue! This issue is being locked to prevent comments that are not relevant to the original issue. If this is still an issue with the latest version of Ionic, please create a new issue and ensure the template is fully filled out. |
Bug Report
Ionic version:
[x] 4.x
Current behavior:
There are three errors by following the 4.7.0 updating guide:
First problem:
Second problem, the migrate command doesn't work:
The third problem when I run ionic serve even I have that package installed with -D:
Expected behavior:
Follow the guide without issues I suppose
Steps to reproduce:
npm install @ionic/angular-toolkit@2.0.0 -D
npx ng update @angular/core @angular/cli
npm i @angular-devkit/architect@latest @angular-devkit/build-angular@latest @angular-dev
Other information:
Ionic info:
The text was updated successfully, but these errors were encountered: