Skip to content
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

Open
AaronSterlingGENEICD opened this issue May 17, 2022 · 11 comments
Open

Support for Angular 13 #1589

AaronSterlingGENEICD opened this issue May 17, 2022 · 11 comments
Labels
enhancement New feature or request

Comments

@AaronSterlingGENEICD
Copy link

AaronSterlingGENEICD commented May 17, 2022

🧩 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.

@AaronSterlingGENEICD AaronSterlingGENEICD added the enhancement New feature or request label May 17, 2022
@SanderElias
Copy link
Contributor

Angular 13 supports is coming with the next version. (available under the @next flag)
As I'm currently committed to another project, this has to wait.
Sponsoring/funding will help speed things up.

@codev911
Copy link

codev911 commented Jun 3, 2022

hi there, angular version come with version 14 now, i hope scully support with them.

@fredericbirke
Copy link

fredericbirke commented Jul 3, 2022

@SanderElias
Can I somehow help you with the angluar 13/14 support? I would be willing to invest time, if this is a task that is doable for people who haven't worked on scully, yet.

@SanderElias
Copy link
Contributor

Well, the v3 branch is out of sync with main, and needs to be synchronized, without losing any of the new stuff.
This is going to be a painful merge, and I currently don't have the bandwidth for it. Once that is done, there is only some testing and fine-tuning needed, which I can actually do.

@fredericbirke
Copy link

fredericbirke commented Aug 11, 2022

With the v3 branch you mean the branch with the name next and it needs to be rebased to main?

@SanderElias
Copy link
Contributor

SanderElias commented Aug 11, 2022 via email

@grenobnik
Copy link

Any news on this "enhancement"?

@PassageNick
Copy link

Looking for news here as well -- I'd help if I could, but I'm not that good. ;-)

@Sergiobop
Copy link

I think @SanderElias is working on it (#1617)

TY!

@AaronSterlingGENEICD
Copy link
Author

@SanderElias could you or someone on the team post an update on this please? Thanks very much.

@fredericbirke
Copy link

fredericbirke commented Feb 19, 2023

@SanderElias
I rebased the next branch on current main, the result can be seen here #1649
Everything is building fine and all test cases run through.
Is there anything else I can help with?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

7 participants