-
Notifications
You must be signed in to change notification settings - Fork 256
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
Support for Angular 13 #1589
Comments
Angular 13 supports is coming with the next version. (available under the @next flag) |
hi there, angular version come with version 14 now, i hope scully support with them. |
@SanderElias |
Well, the v3 branch is out of sync with main, and needs to be synchronized, without losing any of the new stuff. |
With the v3 branch you mean the branch with the name |
Yes, it is indeed in the Next branch.
Op do 11 aug. 2022 om 11:46 schreef fredericbirke ***@***.***
…:
With the v3 branch you mean the branch with the name next?
—
Reply to this email directly, view it on GitHub
<#1589 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAJQ6O7V7XFTWLQAJTCLJFLVYTDWRANCNFSM5WDXTLOQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Any news on this "enhancement"? |
Looking for news here as well -- I'd help if I could, but I'm not that good. ;-) |
I think @SanderElias is working on it (#1617) TY! |
@SanderElias could you or someone on the team post an update on this please? Thanks very much. |
@SanderElias |
🧩 Feature request
Description
Apologies if this already exists somewhere, but I didn't see it after a search. Are there plans to support Angular 13?
Describe the solution you'd like
The sticking point for our install appears to be @angular/platform-server@12. It would be nice to move past that, if not all of 13 is feasible.
Describe alternatives you've considered
We're currently npm-updating with --legacy-peer-deps for a proof of concept in nonprod. We started talking about downgrading to Angular 12 or not using scully, which led me to post this here.
The text was updated successfully, but these errors were encountered: