-
Notifications
You must be signed in to change notification settings - Fork 5
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
Update .nvmrc file with correct Node Version #195
Labels
internal development
Not user-facing work - developer experience
Comments
seyilonge-ps
added
the
internal development
Not user-facing work - developer experience
label
Aug 9, 2024
Can you add to the steps to fix "Make unit test to ensure the node version in the README matches the one in the .nvmrc? I'm sure this will happen again if we don't fix this. Thanks for finding this and opening a ticket for it. |
seyilonge-ps
pushed a commit
that referenced
this issue
Aug 23, 2024
* Updated `.nvmrc` and `README.md` files with correct Node version * Added `engines` property to `package.json` to specify Node and npm version ranges
seyilonge-ps
pushed a commit
that referenced
this issue
Aug 23, 2024
* Updated `.nvmrc` and `README.md` files with correct Node version * Added `engines` property to `package.json` to specify Node and npm version ranges * Added `.npmrc` file and set `engine-strict` property to `true`
seyilonge-ps
pushed a commit
that referenced
this issue
Aug 23, 2024
Closes #195 * Updated `.nvmrc` and `README.md` files with correct Node version * Added `engines` property to `package.json` to specify Node and npm version ranges * Added `.npmrc` file and set `engine-strict` property to `true`
seyilonge-ps
pushed a commit
that referenced
this issue
Aug 23, 2024
Closes #195 * Updated `.nvmrc` and `README.md` files with correct Node version * Added `engines` property to `package.json` to specify Node and npm version ranges * Added `.npmrc` file and set `engine-strict` property to `true` * Updated Node version for GitHub actions
seyilonge-ps
pushed a commit
that referenced
this issue
Sep 3, 2024
Closes #195 * Updated `.nvmrc` and `README.md` files with correct Node version * Added `engines` property to `package.json` to specify Node and npm version ranges * Added `.npmrc` file and set `engine-strict` property to `true` * Updated Node version for GitHub actions * Updated `README.md` file `Setup` section * Added validation script file
seyilonge-ps
pushed a commit
that referenced
this issue
Sep 3, 2024
Closes #195 * Updated `.nvmrc` and `README.md` files with correct Node version * Added `engines` property to `package.json` to specify Node and npm version ranges * Added `.npmrc` file and set `engine-strict` property to `true` * Updated Node version for GitHub actions * Updated `README.md` file `Setup` section * Added validation script file
seyilonge-ps
pushed a commit
that referenced
this issue
Sep 5, 2024
Closes #195 * Updated `.nvmrc` and `README.md` files with correct Node version * Added `engines` property to `package.json` to specify Node and npm version ranges * Added `.npmrc` file and set `engine-strict` property to `true` * Updated Node version for GitHub actions * Updated `README.md` file `Setup` section * Added validation script file * Removed `console.log` from test files * Added `chromedriver_force_download=true` to `.npmrc` file * Updated `chromedriver` from version `126.0.4` to `128.0.1` * Removed `git add` task from `lint-staged` run script
seyilonge-ps
pushed a commit
that referenced
this issue
Sep 5, 2024
Closes #195 * Updated `.nvmrc` and `README.md` files with correct Node version * Added `engines` property to `package.json` to specify Node and npm version ranges * Added `.npmrc` file and set `engine-strict` property to `true` * Updated Node version for GitHub actions * Updated `README.md` file `Setup` section * Added validation script file * Removed `console.log` from test files * Added `chromedriver_force_download=true` to `.npmrc` file * Updated `chromedriver` from version `126.0.4` to `128.0.1` * Removed `git add` task from `lint-staged` run script * Updated chrome browser version for download in github `push-actions.yml` file
zoltan-dulac
added a commit
that referenced
this issue
Sep 9, 2024
…with-correct-node-version (#195) Update .nvmrc file with correct Node Version
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The Node version in the
.nvmrc
file shows20.4.0
while theREADME.md
file has20.11.0
. Runningnvm use
followed bynpm clean-install
results in errors.Running
nvm list
provides a list of Node versions shown belowVersion
20.11.0
in theREADME.md
file is not listed. Best to use the most recent version in the list closest to the one specified in theREADME.md
file, which is version20.15.0
.Steps to fix:
.nvmrc
file to20.15.0
README.md
file to20.15.0
README.md
matches the one in the.nvmrc
The text was updated successfully, but these errors were encountered: