You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's very common to find projects that declare the preferred Node.js version in a .nvmrc or .node-version file in the project root. There are many tools that look up for those files to set themselves up and this feature is not one of those, unfortunately.
It would be nice if this feature would try to define the desired version based on those files (in that order) if no version is provided via configuration before falling back to LTS.
The text was updated successfully, but these errors were encountered:
It's very common to find projects that declare the preferred Node.js version in a
.nvmrc
or.node-version
file in the project root. There are many tools that look up for those files to set themselves up and this feature is not one of those, unfortunately.It would be nice if this feature would try to define the desired version based on those files (in that order) if no version is provided via configuration before falling back to LTS.
The text was updated successfully, but these errors were encountered: