What do you do when you are working on npm-based project and encounter an issue with one of your dependecies?
The easiest way and actually most d...
For further actions, you may consider blocking this person and/or reporting abuse
This article is so helpful, thanks for sharing! <3
Very good solution, thanks a bunch @zhnedyalkow
Very useful. Thanks for sharing.
Nice to hear that!
One note you can try to color the snippets with Github like code blocks. (triple backticks and name of the language).
Great, I did not know that. Thank you, I will update the post tomorrow
How do you patch a package with @ in the name eg @namespace/package?
Probably its not relevant for you anymore, but can help to others :)
from official doc.
Thanks, this helped me.
so there is no way to run a patch when we run
npm install --production, because running npm install will ship the dev deps with the application. any suggestions?But is this safe for production apps ? Like medium scaled ones with number of users ?
Yes, it is safe
While running
yarn patch-package packageNameit gives the following errorRequest failed \"401 Unauthorized\I have deleted the registry and npmrc still no luck
What if I need to change something in package.json ? due this is being executed in postinstall any patch-changes in package.json are useless :(