Skip to content
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

'[error] Node.js version is too low.' - but my version too high #1110

Closed
jochenvanwylick opened this issue Jan 15, 2019 · 3 comments
Closed

Comments

@jochenvanwylick
Copy link

While running ( func start ) my function - I get the following error message:

[error] Node.js version is too low. The version you are using is v11.6.0, 
but the runtime requires an Active LTS or Current version (ex: 8.11.1 or 10.6.0). 

For deployed code, change WEBSITE_NODE_DEFAULT_VERSION in App Settings. 

Locally, upgrade the node version used by your machine 
(make sure to quit and restart your code editor to pick up the changes).). node exited with code 1

As you can see - I'm running 11.6.0 at the moment, the error states the version is too low, whereas - in fact - mine is too high.

So the error is a bit off of course, but also, I really would prefer not having to downgrade my version of Node. So is the version check code wrong and is this an error, but the could would still run? Or do I need to install really THAT specific version?

@ConnorMcMahon
Copy link

This was just an incorrect error message. It looks like it was already fixed in the code, and should be fixed in the next release of the Node language worker.

@ConnorMcMahon
Copy link

Sorry, to miss the actual part of your question: to the best of my knowledge, the version does need to be that specific major version when running locally (i.e. you need to have node version 8 or version 10 on your machine). This is best practice anyways, so that when you test locally, it is running the same major version as in your production environment.

You can install multiple versions of Node side by side, and use a tool like nvm to easily switch between them.

In general, our policy is to support LTS major versions. As you can see 11 is not an LTS release, so we will not be supporting it in Azure Functions. I hope that this addresses your question.

@jochenvanwylick
Copy link
Author

Got it - thanks !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants