I have the latest versions of Node and NPM installed, using which I installed Angular/cli, but it's shooting me with following errors: angular/cli and npm versions not compatible with current version of node.
I suspect that I may(not) be installing out of the proper directory. But at this point, what else can I do? thanks.
Please check: Screenshot with details of the issue
I also faced a similar problem, but the solution was quite simple : my path was too long.
I shortened it a bit (two directories down) and then I did the install again with success.
Here are the reqs.
Both the CLI and generated project have dependencies that require Node 6.9.0 or higher, together with NPM 3 or higher.
You are using the latest node.js 9.2
you need to uninstall or rollback to 8.9 !!
Here is a guide
https://github.com/angular/angular-cli
Hope this solves it for you.
I faced a similar problem with angular/cli version not compatible with the current node version. This generally happens when you are upgrading from lower version of Angular to any other higher version.
You can try following steps:
npm outdated --> To list latest and current package details in local application.
npm update --> to update the local packages.
If it still doesn`t work,
Try deleting the 'node_modules' folder and install dependencies of fresh:
npm install
You can then check whether all packages, including the cli is not outdated.
Related
i can't install react-native-lottie throwing error compatatible version for lottie-react-native CocoaPods could not find compatible versions for pod "lottie-ios"
as per the error says we need to go for
npm i lottie-ios#3.1.8 lottie-react-native#3.5.0
cd ios
pod install
Issue resolved!
If you get something like this,
[!] CocoaPods could not find compatible versions for pod "lottie-ios":
In Podfile:
lottie-ios (from `../node_modules/lottie-ios`)
lottie-react-native (from `../node_modules/lottie-react-native`) was resolved to 3.5.0, which depends on
lottie-ios (~> 3.1.8)
Then we can resolve it by the following steps,
Open terminal in root folder of your react native project.
Execute the following commands to install lottie-ios and lottie-react-native packages with the specified version of the cocoa pod error.
npm install lottie-ios#3.1.8
npm install lottie-react-native#3.5.0
After these package addition move to ios folder and run pod install.
cd ios
pod install
Solved this issue by uninstalling the previous installed Lottie version and then
1- yarn add lottie-react-native#4.0.3
2- yarn add lottie-ios#3.2.3
You need to upgrade your platform :ios version in your PODFILE
In my case,I changed platform :ios from 10 to 11, and everything worked well
It depends on the version of react-native version that we use. For me, it's npm i --save lottie-react-native
npm i --save lottie-ios#3.2.3
since, my react-native version is 0.68.2.
You can check the compatible version for your react-native version from the link below:
https://www.npmjs.com/package/lottie-react-native
Hope this helps !
We need to go for:
npm i lottie-ios#3.1.8 lottie-react-native#3.5.0 cd ios pod install
If you want to use the latest version of lottie-react-native with react-native version of >=0.66, add lottie-ios#3.2.3
>= 0.66 latest 3.2.3
Related link: https://github.com/lottie-react-native/lottie-react-native#versioning
I am following the following guide from GitHub Here but when I enter npm init I keep getting the error:
Sorry, there's a problem with nodist. Couldn't resolve node version
spec %s: %s 11.13.0 Couldn't find any matching version
I have followed the previous steps and set the version to v10.15.3, but the error keeps appearing every time I use nvm. I have also set the version to v11.13.0, as this is what the error is requesting, but I still get the same result. Installed versions include: 11.13.0, 10.16.0, 10.15.3, 8.11.2, 0.12.0
Any help with this would be much appreciated!
There are several reasons which can cause this problem:
If due to some reasons like poor internet connection your node or npm versions you have downloaded are corrupted. In this case you need to remove the files .npm-version-global and .node-version-global as well as empty the folders v, v-64 and npmv within the installation of the Nodist folder.
You have a local version of the node specified in .node-version file in the root directory of your project. In this case you need to install that version by nodist local XXX where XXX is the version of the node in .node-version file.
In my case, the problem was that I had a node version specified in my code repo that didn't match the node version installed on my machine. I needed the updated node version on my machine, so
I opened file explorer to the root of my repo.
I opened .node-version and edited the version number to the updated version I needed.
npm cache clean --force to start with a fresh cache. (Note: Others have said that npm cache clean --force is outdated, but this command worked for both my teammate and for me using npm version 6.9.0.)
npm install to reinstall my node modules.
npm run build and I had a clean build. Yay!
For Node 18 and npm 8.19.1, I found the advice at https://github.com/nullivex/nodist/issues/252#issuecomment-1170897428 useful.
I was getting cb.apply errors, and problems with #npmcli/arborist and libnpmfund, but I created those two links from the list.
I was using npx. This installs an old (v 5.8) version of npm inside its node_modules. That npm contains graceful-fs inside its node_modules. The cb.apply error was coming frome graceful-fs's polyfill.js.
I installed the latest version of graceful-fs, and copied the newer polyfill.js into the abovementioned (child of npm's) graceful-fs. This seemed to fix the problem for me.
I have trouble with installing dependencies in my project. Gulp-sass version is 2.0.4. When I try to install with npm install I'm getting error 404 with node-sass v3.13.1. There is no link for it. I've also tried to insert source file of node-sass v3.13.1 but it's not working. I know the trouble is with link, but is there any way to get around this?
Node-sass is a c++ bridge so particular versions are only supported for some versions of NodeJS. In this case, you are running a new version of Node, that older version node-sass doesn't support. Newer versions also provide better error messages for this.
I am trying to install Satellizer.
But getting error.
Can you guide me to understand whats this error is, and how can I fix this.
I have node version v5.1.0 and npm version 3.5.2
Looks like you have the Satellizer as a decency inside your package.json
Or
That the project name is the same of one your depended package(s)
If it not a depended package, there used to be some error with npm v3.5.X so try to update your npm version and then re-install it.
I would also recommend to test it with node v4.X since v5 might contain those kind of bugs
See title. I searched all across the internets and could not find a firm answer.
The reason I want to use npm3 is because I am working in a Windows environment and I am hitting the dreaded too long path name. Migrating off Windows is not a viable option at this time.
Also, I can not upgrade to node 5.x because I use the karma test runner, which is not yet supported on node 5.x
So, I want to use node 4.x with npm 3.x.
I have successfully updated my machine, using the slick npm-windows-upgrade package, to use npm 3 with node 4.
After the upgrade, I did see a couple issues with karma not realizing jasmine/phantomjs was available. The workaround was simply to install both those packages locally.
Yes. The npm 3.x is compatible with node 4.x.
In fact, any node >= 0.8 is okay.
This has been documented in
https://www.npmjs.com/package/npm#important
You need node v0.8 or higher to run this program.
And more, I suggest you to use the nvm
https://github.com/creationix/nvm
It very easy to switch in various node environments with nvm.
Your jasmine/phantomjs is references by peerDependencies, npm 2.x will install it if missing, and an error will be reported if found version conflict by multiple package.
As you known ,the npm 3.x flatten the package dependencies, peerDependencies will print a line of warn message only(will not be instal), you should manually include peerDependencies in your package.json file, this means it is you that decide which version should be installed.