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
Angular 13 support #4178
Comments
Any idea when Angular 13 will be supported for the Bootstrap 4.x version? We're trying to update to Angular 13 but a few libraries have conflicting peer dependencies. It would be great to bump the versions and target ng 13 if it's not difficult. Thank you very much. |
@maxokorokov any thoughts on when the move to rxjs 7.4 might happen? This is possible in Angular 13, but rxjs is declared as using |
@terencehonles we'll do the same as all Angular packages and have |
@terencehonles several issues we're currently facing:
I should do the |
Do you want to use the prerelease as mentioned in angular-eslint/angular-eslint#780 (comment) ? I could open a PR for that, but not sure if you'd want to manage that yourself. |
Also, looking at Same comment about opening a PR for that and that could be done on |
ng13 |
I believe this is supposed to be
That's specifically for Karma, but not sure if the support was just dropped because there didn't need to be 2 different packages or if something else changed. |
I got with #4183 by pulling in angular/angular#44016. I wasted a bit of time trying to get jasmine to run the test as an ESM, but then I saw the change on Angular's side 😅. |
@maxokorokov |
@angular-eslint/angular-eslint v13 just dropped FYI https://github.com/angular-eslint/angular-eslint/releases/tag/v13.0.0 (EDIT: I thought I'd test this, and now you're faced with |
@maxokorokov hopefully to save you some time, I thought I'd upload the results of my testing. master...internalsystemerror:feature/ng13 I've upgraded The karma tests pass locally and the only thing outstanding would be linting errors which I'm unsure how you wish to resolve:
|
For info, I have opened angular/angular-cli#22220 to fix the issue related to code coverage in e2e tests. |
Hey guys, do you have any ETA in mind for the 11.0.0 release? |
For info, I have opened #4193 to re-enable code coverage in e2e tests (now that angular/cli 13.0.4 is released) |
Any update on this. getting errors while trying to install. I used --force to overcome this. |
FYI, StackBlitz now supports Angular 13:
Related StackBlitz issue comment: stackblitz/core#1657 (comment) |
could you please let me know if this is fixed or going to be fixed soon:
|
For info, I have opened #4198 to fix StackBlitz examples now that StackBlitz supports Angular 13. |
v1.3.2 of eslint-plugin-deprecation supports eslint 8, as of v.1.3.0 (yesterday). |
I have opened #4202 to update |
The new 11.0.0 has been released. Thank you all for your efforts ! |
Did you get a fix for this? I'm experiencing this today as well. |
@ETMitch21 If you're installing the bootstrap5 branch you should be posting your questions in #3899. You can still tag a user and quote a comment from this issue in that one if you find it might be helpful context. |
@terencehonles I'm getting the same issues when using version 11
It seems that the support for angular 13 does not support anything over angular 13.0.x |
@adrianord I've been using this version since it was released with no issues. Currently on Angular 13.2.2. I suggest you open a new issue if you're certain it's an issue with this package. |
@adrianord Did you try deleting your package-lock.json and your node_modules folder, and then re-installing your dependencies? I always get those kinds of errors when upgrading Angular unless I do that. |
This is a result of a badly designed package manager. See e.g. #3970 (comment) or a billion similar issues. Use |
@internalsystemerror @Alex3917 @devoto13 Thanks for the help guys, I was looking for an issue about this, I guess I was just using all the wrong keywords. This was on a brand new angular project, using |
Facing same error with Angular v13.3 |
Facing same error with Angular v14 |
Latest releases:
Internal issues:
eslint-plugin-deprecation
doesn't supporteslint 8
→ usingangular-eslint 12
version at the momentcoverage-istanbul-reporter
→ temporarily disabling custom webpack configunit tests for schematics are broken due to(Fixed in Angular 13.0.2 with build: fix and re-enable schematics unit tests #4183)externalSchematic
calling@angular/localize
ESM issues → temporarily disablingno support for Angular 13 in→ moved to @angular-builders with build: replace ngx-build-plus with @angular-builders/custom-webpack #4180ngx-build-plus
→ no e2e coverage at the momentThe text was updated successfully, but these errors were encountered: