-
Notifications
You must be signed in to change notification settings - Fork 57
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
feat: autoinstall Angular v17 #5367
Conversation
"plugins": [ | ||
{ | ||
"packageName": "@netlify/angular-runtime", | ||
"condition": { "minNodeVersion": "17.0.0" } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this what you meant to do?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nope, it isn't! I meant to do "from angular v17 on, use this". gonna look at how to do that. good catch!´
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's changed since I last worked on it, so I'm afraid I can't help there!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
implemented minFrameworkVersion
in e6298e9
minFrameworkVersion
I'm pretty sure the versioning must already be implemented elsewhere though. We're installing different versions of the Next.js runtime according to which version of next it is, so that logic must be somewhere! It used to be in plugins.json, but I think it's in the CMS now |
We have versioning implemented + configured via |
minFrameworkVersion
Lukas reminded me that we're not using framework-info anymore. Good news, because build-info makes this change a lot simpler! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's better! The new system is so much more flexible. I'm approving this but I reckon I'd wait for a review from Lukas or someone else who knows the detection code better before merging
I'm pretty confident in the approach based on tests. Will merge now in the interest of time, let's address any feedback lukas might have in a follow-up. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
In netlify/angular-runtime#67, we're working on improved Angular support for v17+. This PR adds auto-install for the package.
To be merged after netlify/angular-runtime#67 is done + released.