Add devEngines parameter to package.json#2721
Add devEngines parameter to package.json#2721sm17p wants to merge 1 commit intoGraphiteEditor:masterfrom
devEngines parameter to package.json#2721Conversation
This is a part of maitaining interoperability in the future in accordance to openjs-foundation/package-metadata-interoperability-collab-space#27, with the goal to streamline dev and CI/CD enviroments.
Keavon
left a comment
Keavon
left a comment
There was a problem hiding this comment.
What benefit does this provide? I'm wary of any unsolicited changes to our dev tooling and CI, especially when it's working fine currently.
|
Firstly, this resolves the confusion of which version of Secondly, this won't break anything per se, the Eventually, contributors will be relying on these fields to auto setup their environment once it gets adopted in the ecosystem. |
|
I would prefer to wait a few years before this becomes an actual standard. From what I can tell, this is bleeding-edge, speculative, and not even implemented yet. Graphite's dev environment prescribes specific tools and doesn't intentionally support using yarn/pnpm/etc. anyways. Feel free to bring this up again once this becomes a widely adopted standard and including this solves an actively encountered pain point. Thanks. |
2 participants
Description
The
devEnginesfield is now supported by npm and corepack.The goal is to streamline dev and CI/CD in accordance to openjs-foundation/package-metadata-interoperability-collab-space#27
Open to discussion
Maybe, once the below mentioned issues and PRs are resolved the project can migrate away from
.nvmrcVersion Manager & CI/CD
devEnginesacceptance tracking:devEngines.runtime support for detecting the runtime environment nvm-sh/nvm#3595devEngines.runtimefiled inpackage.jsonSchniz/fnm#1433devEnginesfield volta-cli/volta#2050devEnginesfield actions/setup-node#1283