i using react-native-pdf but in new version it use react-native-blob-util and when i install react-native-blob-util its crash.
i read from stackoverflow and google, that it's better to downgrade the react-native-pdf because, the downgrade version of react-native-pdf why don't use react-native-blob-util.
now i have react-native-pdf version = 6.4.0
now i want to downgrade to react-native-pdf
version = 6.2.0
please someone help me, thankyouu
You can install any npm module by mentioning the version as well. Remove the package from package.json first, then
npm i react-native-pdf#6.2.0
I had faced the same issue last week, so I started using react-native-view-pdf package, its similar and not much code change is required, you can try it.
You can just edit your package.json. Just edit your "react-native-pdf": "6.4.0" to "react-native-pdf": "6.2.0". And after that run npm install or yarn
Related
I I'm facing the issue for install react- currency- format because of latest version of react 18 i can easily install with the help of force save....but i have doubts if i m doing this then it will creat issues with my system
currently the react-currency-format does not work with the 18.0.0 and above to get the react-currency format to work you will need to downgrade your react to react ^17.0.0 in your package.json file after deleting your package-lock.json
another option is to add --force to the end of the install command like so
npm install react-currency-format --save --force
or you can also use
npm i react-currency-format --save --force
Your Welcome
Welcome to the community! Here is a set of questions can work as clarification, for your kind information.
Ques: Is react-currency-format well maintained?
Ans: We found indications that react-currency-format maintenance is sustainable demonstrating some project activity. We saw a total of 20 open source contributors collaborating on the project.
Ques: Is react-currency-format safe to use?
Ans: The npm package react-currency-format was scanned for known vulnerabilities and missing license, and no issues were found. Thus the package was deemed as safe to use.
Hope both of above mentioned q/a gives you a "aha" moment.
Reference: https://snyk.io/advisor/npm-package/react-currency-format
npm version 7.5.4 detected. The Angular CLI temporarily requires npm version 6 while upstream issues are addressed.
Please install a compatible version to proceed (npm install --global npm#6).
For additional information and alternative workarounds, please see https://github.com/angular/angular-cli/issues/19957#issuecomment-775407654
Update
The issue is closed and the problem solved
NPM 7.5.6 or greater.
Angular CLI 9.1.15, 10.2.3, 11.2.2, 12.0.0-next.2 or greater (within each major version).
if you still having problems use:
Hi you can bypass the error using ng new --skip-install <-- Workaround
Unfortunately is not the best approach is downgrade node and npm , stay tune here is the open issue :https://github.com/angular/angular-cli/issues/19957
If you want to use schematics the workaround will doesn't work ,please downgrade
I am fairly new to versioning a library, I wanted to get a clarity on my concern and please explain how does npm work.
I am trying to build a library and publish it to my organization npm registry. Now I have an alpha release which is already available in nexus and I did an npm install and the library works fine.
Now I when I create a stable release and make the library available for my organisation to use, when this happens the version tag will be updated to v1.0.0 and when I do an npm install the latest stable version will be available.
Post this, if I create further more alpha builds the version now has an alpha build tag appended to the version. Now when I do an npm install in a fresh project setup which version will I get:
stable version
new alpha version
I am a new to this, if anyone can explain how npm install will work and what version will I get that will be super helpful.
Thanks
What npm i will do for you, depends on what you stated in package.json.
{
"dependencies":{
"foo":"1.0.0", //match version exactly
"baz":">1.0.2", //must be greater than version
"elf":"~1.2.3", //everything from 1.2.3 to <1.3.0
"thr":"^1.2.3", //from 1.2.3 to <2.0.0
}
}
More details here
If you want to know the exact version of the package installed after npm i you could look it up in package-lock.json
I'm trying to install a package 'Kurento-client' via npm but it gives error in installing its own dependencies (bufferutil and utf-8-validate). Error also mentions 'node-gyp rebuild'
Here is the screenshot of the error:
Can you please tell, what should I do or change?
When I install those 2 dependencies separately (bufferuil and utf-8-validate), they install successfully with the latest version.
But the Kurento-client is installing their old version. I don't know why. I need only kurento-client to be installed.
After searching for a while, I solved it by dropping the npm version. The reason is that some packages have dependencies which they need to install, and in our case, those dependencies were of the old version which cannot correlate with the newer version of npm. Either you have to update those ones separately or drop your npm version. Hope it helps someone!
I upgraded to --latest but want to downgrade to a specific version due to compatibility issues.
Just specify the version number like so.
npm install jspm#1.0.0