I'm pretty stuck trying to publish a package -- I've tried it both from local file system and github repos url - same issue.
I've created a detailed issue on the github npm repo here, but I'm getting crickets.
Wonder if someone here might scan the issue and help me out?
Thanx.
Per comment from Ibis Liven (github NPM issue #19404), I created an account on the NPM website and then the publish worked from the command line as expected.
Seems the adduser command is broken.
Related
Vite manifest not found at: /app/public/build/manifest.json (View: /app/resources/views/layouts/app.blade.php) (View: /app/resources/views/layouts/app.blade.php)
not sure if you've made it but I came across your post, so just wanted to share what I did.
I ran
npm i
npm run build
in .gitignore, I deleted
/public/build
then push it to master.
Hope this helps.
It's first time I'm trying to use Actions in GitHub to load a package on npm.
My workflow gets error because of:
npm ERR! code E404
npm ERR! 404 Not Found - PUT https://registry.npmjs.org/github-custom-module - Not found
npm ERR! 404
I noticed that also trying to reach out by browse bar https://registry.npmjs.com/ or http://registry.npmjs.com/ and it responds something like:
{"db_name":"registry","engine":"couch_bt_engine","doc_count":2594600,"doc_del_count":334,"update_seq":12737068,"purge_seq":0,"compact_running":false,"sizes":{"active":52390186030,"external":150891609029,"file":52550172912},"disk_size":52550172912,"data_size":52390186030,"other":{"data_size":150891609029},"instance_start_time":"1640854262658073","disk_format_version":7,"committed_update_seq":12737068,"compacted_seq":12733464,"uuid":"d8db915449574fe1dbb729e34426a075"}
just wondering if someone got in trouble for the same reason and eventually how to fix it!
Thank you very much!
Since your npm package is in a private repo, your Github action may not have access to it. There are two approaches to solving this ->
The easy way
You can use a read only access token in the dependency list in the package.json file to install the packages. This will require changing the code base but it trivializes the CI part. Bear in mind that if the token expires or is deleted your builds will start failing.
The not so easy way
The other way is to again create an access token for the npm registry and then
adding it to the Github Secrets instead. So lets say we store it in
NPM_TOKEN then in your action file you could simply add this to the env
steps:
- run: |
npm install
- env:
NPM_TOKEN: ${{ secrets.NPM_TOKEN }}
You also need to create a .npmrc file in the root of your project with a single line using the env variable to set the auth token.
//registry.npmjs.org/:_authToken=${NPM_TOKEN}
The npm cli will replace the value from the environment in so your secrets are safe !
Several days ago I published a package to npmjs, https://www.npmjs.com/package/pluralize-ru-ts the package is public, i'm pretty sure that the package.json is correct, when i try to npm i pluralize-ru-ts package installs fine, i get no errors.
But the package still doesn't apears in npmjs search in npmjs.org and in npm search pluralize-ru-ts(returns No matches found for "pluralize-ru-ts")
Any ideas, what am i doing wrong?
Just tried npm search pluralize-ru-ts and successfully found you package.
If you are still facing this problem, maybe there are some caching issues.
Screenshoot
Installing an NPM package (in this case 'zos') hangs at :
>npm install zos
fetchMetadata: sill resolveWithNewModule http-https#1.0.0 checking installable status
Seems kind of strange as this has only recently started occurring. Other packages seem not to have this issue...
I am using the following environment:
Arch Linux
Node v11.9.0
NPM v6.9.0
I can install other npm packages without issues (eg, lodash, truffle, web3)
OK, I managed to fix the issue... last week I was having some issues with internet access in a new location with wifi so I had to hack around a bit with my /etc/resolv.conf file to get general internet access again... turns out that while that fixed my general browsing it had a knock on effect on npm installs!
So in summary to fix the issue I replaced my /etc/resolve.conf file which had only the following line in it:
# Generated by NetworkManager
nameserver 192.168.0.1
with a previous version of the file I had saved which had the following contents:
nameserver 127.0.0.53
options edns0
And Walah! Everything works again, including the 'npm install zos'....
Thanks to anyone who was looking into this for me!
Cheers
Rick
I know this issue has been discussed in an old post. But in that scenario the developer was importing socket.io via a script tag. I am getting the same error on my local build and I have installed socket.io using npm.
Has anyone had a similar issue? How can this be corrected?
Turned out to be an npm cache issue for me. After several attempts I was able to resolve this by clearing my npm cache, deleting all of the modules, and then re-running npm install.