i want to install socket.io version 1.0.0 but npm gives me the error "version not found"
It is possible not to publish every incremental version of an package. It is possible that version 1.0.0 was never published, therefor you cannot install it. try:
$npm install#1.0.1
Related
I am trying to install all the dependencies of my angular application.
Now once I enter npm i to install all the dependencies I am receiving this error message.
Initially, I thought this is an issue with Installing Angular CLI globally using npm, so I run the
npm install -g #angular/cli
and I received this message -
Now anyone has any idea what is wrong with the angular CLI message and also what do I need to do to successfully install the npm i to my angular application successfully?
Angular requires an active LTS or maintenance LTS version of Node.js:
https://angular.io/guide/setup-local#prerequisites.
So install LTS releases of Node.js: https://nodejs.org/en/about/releases/
yes you have the wrong version of #nguniversal and its not compatible with the current version of angular you have which looks to be 12.x.
so you have to type for good measure:
if any have an error its because one of the packages are not there and that's okay with the next step
npm uninstall #nguniversal/common
npm uninstall #nguniversal/builders
npm uninstall #nguniversal/express-engine
now type
ng add #nguniversal/express-engine
that's it it will add itself - there is still a lot of work post this though so please follow these instructions carefully.
https://angular.io/guide/universal
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 using npm outdated -g --depth=0 to see which globally installed packages have newer version. I am getting this:
$ npm outdated -g --depth=0
Package Current Wanted Latest Location
bower 1.6.8 1.6.8 1.7.1
jshint 2.8.0 2.8.0 2.9.1-rc2
jspm 0.16.13 0.16.13 0.16.19
npm-windows-upgrade 1.0.1 1.0.1 1.2.0
typescript 1.7.3 1.7.3 1.7.5
I can not update any of those packages. npm update -g does nothing. Why Wanted field is has lower version than Latest? I am using windows 7, node 4.2.1 and npm 3.5.2
Since these are global packages there is no package.json to direct their update policy. By default "wanted" version is the same as installed or "current" for global packages. That means npm update will not update them saying that they are at the most recent wanted version.
In order to update them use npm -g install .... Install will use "latest" version from the repository.
npm update -g shouldn't do "nothing" -- you should try npm update -g --verbose and see what that has to say.
I've had to run npm update -g a few times in succession to get it to update everything to the latest.
I just ran into this same issue and had a different solution not yet mentioned. My issue was that my package.json had semantic versioning constraints associated with versions. Given your package bower, for example, with a current/wanted version and of 1.6.8 and a latest version of 1.7.1, it could be possible that your package.json file shows:
"dependencies": {
"bower": "~1.6",
}
Running npm update bower would not update bower past version 1.6 to version 1.7 because of the ~ prefix; to get around this you can run npm install bower#latest to bypass the semantic versioning constraints.
Ive been trying to install phonegap for hours now. For some reason by default it installs version 0.9.4 (when I do npm install -g phonegap). If I specify to use latest version (npm install -g phonegap#5.0.0-0.28.1) I get tonns of errors for almost every dependency out there. Tried reinstalling node, removing modules, clearing npm cache, etc.
Windows 7
Node version 0.12.5 (x64)
Npm version 2.11.2
I had this problem before with my Mac
to fix this, i just simply ran
npm update -g phonegap
and behold it updated itself to 5.0.0
I´m facing a funny problem. I wrote a small module with some function to work with the xbee-api in nodejs. I created a git repository and published the module at npm website. I can see on github and npm the newest version (0.0.4) but neither npm install nor npm update install the new version.
Is there some time buffer before installing a new version? I also tried with --force but still 0.0.2 is the latest version which will be installed.
EDIT:
I found out that changing in package.json from ^0.0.2 to * the newest version will be installed.
But from my understanding, ^0.0.2 should install also all minor releases below 1.0.0. Is this correct?