question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Specified version of Node in .nvmrc is incorrect

See original GitHub issue

Describe the problem and steps to reproduce it:

STR:

  1. Cd into the addons-frontend repository
  2. In a shell, run nvm use
  3. Next, run yarn in the same shell
  4. Observe the error message from yarn

Recently I found that the nvm docs had a section for automatically switching node versions if a .nvmrc file existed in the current shell directory for zsh.

After successfully setting that up, I noticed that the version for this project found in .nvmrc is still 6 when yarn requires >= 8.10.

See below for more details:

screen shot 2018-12-18 at 9 28 17 pm

What happened?

yarn was unable to install dependencies for this project.

What did you expect to happen?

All dependencies would be installed, if necessary.

Anything else we should know?

This should be reproducible on Mac, Windows, and Linux if nvm is installed.

As per the docs found here, the requirements state that users must have Node 8.x which is the current LTS. Let’s also update that to say something like Node 8.10!

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Comments:6 (6 by maintainers)

github_iconTop GitHub Comments

3reactions
rebmullincommented, Dec 20, 2018

I think we want to keep the same format that we already see:

  • 8.x in the docs (to match the release names here)
  • 8 in the .nvmrc file.

We are not on 10 yet but it seems like we should do that soon!

@willdurand @kumar303 - what do you think?

3reactions
rebmullincommented, Dec 20, 2018

I never noticed this .nvmrc file:)

Read more comments on GitHub >

github_iconTop Results From Across the Web

Automatically switch to correct version of Node based on project
Looks for a .nvmrc file in your current directory, every time you cd . If one is found, it loads the version via...
Read more >
Specify required node version in readme, package.json or ...
Specify required node version in readme, package.json or nvmrc file ... Attempt to run npm install with the incorrect version.
Read more >
Node version doesn't loaded via .nvmrc : WEB-45434
In the project is specified via .nvmrc file v14.1.0 (default Node version is 11.15.0) If try commit changes, it's raised error with incorrect...
Read more >
Specify Node Versions with .nvmrc - David Walsh Blog
A project with this .nvmrc is specifying that Node.js v16 should be used. Any developer could then run nvm use to download, install,...
Read more >
Manage build dependencies | Netlify Docs
A build's Node.js version is initially determined by the default version ... Add a .node-version or .nvmrc file to the site's base directory...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found