-
Notifications
You must be signed in to change notification settings - Fork 876
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 using installing node and yarn version matching the package.json engines property #798
Comments
This is something that we'd love. We have a hard time keeping up with our frontend users when they bump versions, and this would really fix that problem. :) Any plans for implementing this? |
I have added support for the node part in #999. Support for npm/yarn is still on my TODO. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Do you want to request a feature or report a bug?
feature
What is the current behavior?
You have to specify the nodeVersion and yarnVersion
What is the expected behavior?
The install-node-and-yarn should support using the version specified in package.json engines for node and yarn.
https://yarnpkg.com/lang/en/docs/package-json/#toc-engines
That could be configured by using "engines" as value for nodeVersion and or yarnVersion.
In such case frontend-maven plugin should install the most recent version matching the version expression in engines for yarn/node
The text was updated successfully, but these errors were encountered: