Working through the setting up of a project that requires the use of gulp. However I am getting the error:
Your dev environment is running NodeJS version v10.13.0 which does not meet the requirements for running this tool. This tool requires a version of NodeJS that matches >=8.9.4 <9.0.0
It seems strange that I should have to go back a version to make the latest version of gulp (3.9.1) work.
Not familiar with this at all so any advice would be appreciated.
Related
when I do mvn compiling for flink source code，I get:
Node.js version v9.0.3 detected.
The Angular CLI requires a minimum Node.js version of eithor v10.13 or v12.0
when I input node -v, the result is 12.18
so,what's the comand to know the Node.js version in angular's eyes?
and where does the old version v9.0.3 come from?
I restart my computer and the error remains.
Thanks for your help.
(Python3.6) appleyuchi#Desktop:~$ which npm
/home/appleyuchi/.nvm/versions/node/v12.18.0/bin/npm
(Python3.6) appleyuchi#Desktop:~$ which nodejs
(Python3.6) appleyuchi#Desktop:~$ which node
/home/appleyuchi/.nvm/versions/node/v12.18.0/bin/node
I compile and get the following message again
Node.js version v10.9.0 detected.
what do you mean by angular's eyes? There is no different node for angular. if it is installed then the node is same for all framework.
Follow this link to check Angular, Node.js and TypeScript compatibility.
https://gist.github.com/LayZeeDK/c822cc812f75bb07b7c55d07ba2719b3
You can use nvm if you want to work with multiple node versions
this link will help in using nvm
https://www.sitepoint.com/quick-tip-multiple-versions-node-nvm/
I am quite new to NodeJS and am planning to upgrade NodeJS version for my current project. The most recent NodeJS LTS is installed using NVM.
I need to keep switching between the current LTS that i am using and the new LTS that has been installed. I understand that i can do 'NVM use' for this purpose. npm-shrinkwrap.json is being used to lock down the npm package dependencies.
I am planning to follow the below approach both in my dev machine and build machine;
Is it okay? If not, please suggest a best approach.
nvm use latest_LTS
Update the package.json to pick the version which is supported by
latest_LTS
npm install
generate testing_build
Whenever i need to generate a build for current release (with the previous LTS NodeJS)
nvm use currently_used_LTS
clear the node modules
npm install (Release npm-shrinkwrap.json)
generate release_build
Thanks
In theory that should work.
However have you considered the option of just doing a point release for the current release_build that does nothing except version-bump node?
You may find (after re-running your tests) that the latest version of node is backwards compatable with release_build (or only requires minor fixes), and you can simplify your life by porting everything to the latest node version, rather than constantly switching
Trying to learn angular recently, but I am stuck in an error of angular. So here it is.
I am using Ubuntu 18.04, installed node latest version via nvm.
But I have "two" nodes in Ubuntu,[default] nodejs which is v8 now, and the node v13.
When I try to create angular project with ng new my-first-project it runs good, but it keeps warning of some deprecated dependencies for example core-js. I upgraded core-js to the latest(forced using sudo). But the deprecation warning did not disappear, I thought to use sudo ng new my-first-project but this time it brings me error
You are running version v8.10.0 of Node.js, which is not supported by Angular CLI 8.0+.
The official Node.js version that is supported is 10.9 or greater.
Please visit https://nodejs.org/en/ to find instructions on how to update Node.js.
How can I change angular's using nodejs -> node?
You have two Node.js versions installed with nvm, v8 and v13. It seems that Node.js v8 is active, you can check this with node --version command line command. If the version is really v8 you have to change it with nvm to v13 using nvm use 13.{x.x} command. The {x.x} should be the concrete installed version. If you don't know the installed versions by heart you can check them with nvm list command line command.
If you change the active Node.js version to v13 with nvm it will be used by Angular CLI and you won't get the above mentioned error.
Installed the Angular CLI using this command
npm install -g #angular/cli
But when creating new project using command
ng new PROJECT-NAME
it shows
You are running version v8.0.0 of Node.js, which is not supported by
Angular CLI v6. The official Node.js version that is supported is
8.9 and greater. Please visit https://nodejs.org/en/ to find instructions on how to update Node.js.
But actually i am using nodejs v9.11.1
See screenshot of my cli
Mostly sounds like a version problem. The new angular cli version requires the latest version of node.
All you need to do is update node and npm to latest version , everything should work fine.
If you are working on windows I'd suggest just going on their site and getting the latest one(currently at the time of this post is 8.11.2). For linux based and mac I would suggest looking for a guide how to get latest version since installing from terminal with something like (apt-get install or yum) will not have latest version you need (can easily be changed with some simple commands)
Also do check the version of node with: node -v
There has also been a naming conflict on linux regarding node vs nodejs see this question.
I have a restriction of using node JS version 6.9.1. I am getting many problems, while using angular cli quick start steps.
after ng serve, browser page will be white, no error in console.
npm start works, but if i change some style/file browser do not not refresh.
if i make any style change, webpack compiled successfully message comes but webserver fails to load page.
When I follow the quick start steps with latest nodejs it works like a charm. Can any one help me in telling, what are the versions (npm, angular-cli), I should use to run it ?
Like
Each Angular/Cli version has limited its compatibility of node versions below a specified release. If you have to use a specific version of node then your best bet would be to find a previous version of the Angular/Cli that will play nicely.
Here you can find all the versions and from there, pick one a little further back in the list and then do a search in google for "Angular/cli version x.x.x node compatibility" to see if there are any known issues.
Once you pick a version that looks good, run
npm install -g #angular/cli#<your version number>.
Once the install is complete run ng help and you'll get feedback right away if the version is still incompatible and you can try a different version.
Just make sure you get rid of the installs you aren't using with npm uninstall -g #angular/cli#<your version number>
for see if angular-cli is compatibility whit your node version installed you can see https://www.npmjs.com/package/#angular/cli/v/6.0.8?activeTab=versions, for example, I have installed node 6.11.2 and I have to use: npm install -g #angular/cli#6.0.0