-
Notifications
You must be signed in to change notification settings - Fork 1.5k
feat(node-version-file): support parsing devEngines
field
#1283
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
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: Ferdinand Thiessen <[email protected]>
Awsome! Appreciate for your work. |
This comment was marked as outdated.
This comment was marked as outdated.
Co-authored-by: Grigory <[email protected]> Signed-off-by: Ferdinand Thiessen <[email protected]>
149b070
to
25df5cd
Compare
This comment was marked as resolved.
This comment was marked as resolved.
@gowridurgad Could we please get this reviewed … |
@HarithaVattikuti anything I can help with pushing this forward? |
I saw you reviewed similar requests @aparnajyothi-y @priya-kinthali maybe you can have a look? |
That's normal for this repo. You can't really do anything to speed up the process |
Description:
Currently if you want to support multiple versions for running (e.g. a library) but enforce a specific version for development you can set
devEngines
with npm 11.This PR adds support for parsing the
devEngines.runtime
field (if it is set tonode
) for allowing automatic setup.Related issue:
devEngines
field inpackage.json
#1255Check list: