Closed manolakis closed 3 years ago
Latest commit: 6fcf949ce6dad5fb3a2e852d8306b34e6470adb2
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
Click here to learn what changesets are, and how to add one.
Click here if you're a maintainer who wants to add a changeset to this PR
can this be a range of "at least v14"? I'm using v15 features in my site
I'm not sure if I'm understanding you. This .nvmrc
should point to the minimal node version required to build this repo. Your site I guess is in another repo and would require the npm packages of this one, but this .nvmrc
is not going to affect to your repo. You can have another .nvmrc
pointing to node v15.
@manolakis you're right, my mistake
not sure who will use that file... 🤔
but we can certainly add it - thx 🤗
I use it! 😅
I use it! 😅
how? do you check it manually and then run nvm? or do you run nvm whenever you go into a directory? 🤔
nvm is executed automatically when I enter in a dir o subdir with the file.
What I did
.nvmrc
file to indicate that node v14 is required in this project