Sometimes, you'll come across a nearly perfect npm package that does almost everything you want. Or perhaps out of all the great features it has, it implements one that just doesn't fit your web app.
And in some of those cases, you may be able to fork it, modify it, and submit a pull request if the feature aligns with that project's goals.
But for those times where a merge is highly unlikely, you can still fork, modify, and publish your own version of the npm package so you can use it in your own live apps.
npm loginwith your username and password. You'll also confirm your public email address.
npm publish --access public. The '--access public' amendment is only needed if you use the '@yourUsername/pkgName', and if it's the package's first publication. Subsequent updates to the do not require the flag.
npm run buildor
yarn build), then run
npm update [package name]to update the package.
Code: 402 You must sign up for private packages : @yourUsername/pkgName: You need to append
--access publicto the end of `npm publish.