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
Update Dependencies to Angular v14 #967
Conversation
- updated @angular libs - updated ng-packagr and created ng-package.json for packaging - updated jest and jest-preset-angular so tests pass
@christopherthielen @oBusk any qualms with merging this and creating v10.0.0 release? |
Any ETA on this? |
Got any updates on this? @christopherthielen @oBusk |
What is the reason for the creation of the ng-package.json? |
Also looks like the test are failing. Can you fix the missing dependency? |
https://github.com/ng-packagr/ng-packagr now requires a separate ng-package.json file rather than including the details in the package.json (you can compare the current README to ng-packagr@v13 Also added dependency for Thanks for your help @wawyed! |
hmm.. not sure what to do with the current error in the CI:
|
Looks like there are conflicting peer dependencies. Before you made that last change it was ok, but with the addition of dev kit it added some to yarn-lock:
There's nothing wrong with the peer dependencies though. Yarn doesn't report anything either. I'm not so sure that test is set up correctly. Looking at that package, I'd figure it should be set up as:
Which does pass. Can you modify the test to include that? |
I updated the |
oh.. I didn't realize the ci.yml file had it's own definition of the But I guess I'm not sure if that or the master branch version of the workflow will be used |
can we approve the workflow again to see if it is fixed @dereekb @wawyed @christopherthielen ? |
I'm not a maintainer, but it looks good to me, fwiw. I have been using your branch on my Angular 14 projects already and haven't run into any issues. |
@wawyed think you can help out? |
@wawyed added angular v14 test project, hoping that should solve the ci errors now |
Found these instructions for updating Angular versions: https://github.com/ui-router/angular/blob/master/add_support_for_new_angular_version.txt Pushed a commit to this PR after following these steps:
Also created a PR in sample-app-angular as per the following instructions:
ui-router/sample-app-angular#771 After the PR is merged, I think the |
For this issue. I noticed something was done to be fixed here ui-router/sample-app-angular@3aad92b Maybe try this same approach? |
I guess we need to fix the mergify config in this project too |
created #968 to update mergify config |
Looks like all CI is passing and I have updated to use the After this is merged, we will need to create a new release (v10.0.0 I would think), as per the instructions here: not sure if I can do this though... @wawyed Once the release is made, I will begin to work on these steps to get https://github.com/ui-router/angular-hybrid updated to angular v14 |
I'll look into it. I just realised I should have squashed the commits... |
@wawyed do you think you can force push to revert these changes and then I can create a PR again that we can squash? Or is it alright that you didn't squash and we can move forward with the release of v10.0.0 now? I am blocked on updating https://github.com/ui-router/angular-hybrid until the v10.0.0 ui-router/angular release is created |
@wawyed can you also create release artifacts for this repo and https://github.com/ui-router/angular-hybrid and have you run |
What do you mean both libraries should be at the latest version? https://www.npmjs.com/package/@uirouter/angular-hybrid version 14 |
Steps:
@angular
libsng-packagr
and createdng-package.json
for packagingjest
andjest-preset-angular
so tests passTests Passing:
Build:
Notes
Should increment version to 10.0.0 after this and create a new release for NPM