Is there are command-line switch to point the npm registry to different url? I have created a template and published to our company's registry. When referring the package, it is referring to https://registry.npmjs.org/. I did install the template locally using
C:\>npm install -g #company/asyncapi-csharp-template
C:\>ag DomainServiceA.yml #company/asyncapi-csharp-template -o ouput
and the error response is
Something went wrong:
HttpErrorGeneral: 404 Not Found - GET
https://registry.npmjs.org/#company%2fasyncapi-csharp-template - Not found
Tbh best if you submit issue here https://github.com/asyncapi/generator/issues as normally it should work.
also try to add --debug flag to understand more what is happening with template usage in generator
I'm currently trying to install the package atom-beautify to my Atom IDE. When attempting to do so I get the following error:
npm ERR! code E500
npm ERR! 500 Internal Server Error - GET https://www.atom.io/api/packages/atom-beautify/versions/0.33.4/tarball
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\User.atom.apm_logs\2022-04-19T03_03_14_465Z-debug.log
I understand that this may be solved with downloading additional command-line tools as I currently only have the Windows default tools and Git.
If anybody could give me any information on how to fix this issue that would be great.
Thanks :)
I believe this is an issue with the Atom servers. Issue opened on Atom github portal.
https://github.com/atom/atom/issues/25417
Issue is from yesterday I think, I try to reinstall Atom several times and change the configuration but the issue persist, I search more information into Atom official blogs and didn't find like the root cause or anything related
Maybe server are down because is not related with the atom basic configuration or apm
Hope to solve soon.
The issue is with Atom servers. any package i tried to install these days fails.
An alternative to install atom-beautify is using its github repo.
So use
apm install Glavin001/atom-beautify
references to my answer
https://github.com/atom/apm/issues/355#issuecomment-116411783
https://github.com/atom/atom/issues/25417#issuecomment-1103834423
Use this to install any atom package available on github
So I'm just setting up my Discord bot in a new machine. I used the latest Node version in LTS and I have Windows Build Tools installed.
But doing npm install, everything is going well until the part when the sqlite3 package is being installed. I have a log here for reference: https://pastebin.com/ktJ8VyZY
And another log straight from PowerShell: https://pastebin.com/d232rjJY
Before I had issues with Python and that has been resolved but right now I cannot pinpoint exactly what is the problem and I've been reading all lines related to gyp and the problem isn't really clear for me so I'm here if anyone can pinpoint the exact problem and the ways to solve it.
Thank you.
Package.json if needed: https://pastebin.com/ACh0mQRe
Image I am cloning the sitecore Habitat project to my local machine.
After cloning while running npm install, I am getting this error. I tired in all possible ways from the stack overflow answers, but did not succeed with answers still its showing errors, if anyone known about this please let me know.
ERROr: **npm ERR! Unexpected token < in JSON at position 0 while parsing near '<!DOCTYPE HTML PUBLI...'**
Just delete
package-lock.json file
It works for me.
I getting error like:
I found this solution in another question and worked for me after I set the registry like this:
npm set registry https://registry.npmjs.org/
Setting npm Registery worked for me
npm set registry https://registry.npmjs.org/
This error means there is a proxy in the middle which is denying you access to the Internet.
The error comes from the HTML page that is rendered from the proxy.
You need to check with your network administration to either allow the connection through (an exception), or you have to configure the variable HTTP_PROXY in your environment, which is like this:
http://username:password#proxy.server.com:port
Having tested npm install in several repos with the same error I ran npm cache clean --force and tried again. This is not as severe a solution as deleting all traces of node and reinstalling from the ground up.
I use an npm registry hosted at work for internal npm packages so couldn't change the registry source.
yes , its happned due to proxy setting, if this problem occurs, please check your proxy setting, in my case npm was getting blocked, You need to check with your network administration to either allow the connection through (an exception), or you have to configure the variable HTTP_PROXY in your environment
You need to check all required npm config setup like:
https-proxy=https://username:password#accessdomain:port/
proxy=http://username:password#accessdomain:port
registry=https://registry.npmjs.org/
//If required also add
msbuild_path=C:\Program Files\Microsoft Visual Studio\2022\Community\Msbuild\Current\Bin\MSBuild.exe
I was getting the same issue. I had un-installed NodeJs and deleted folders npm and npm-cache from Users\username\Appdata\Roaming folder and installed it.
Then set config registry by using command terminal as.
npm config set registry https://registry.npmjs.org/
To give an actual description of the problem and solution:
This happens when the URL set as your npm registry is incorrect (or as others have mentioned, a proxy has got in the way). Either way, you end up trying to download a package from an endpoint displaying HTML, which npm fails to parse as JSON (as one would expect).
You can view the URL for your npm config with
npm config get registry, and set it with npm config set registry https://my.registry.com/ (or https://registry.npmjs.org/ for the public registry)
I tried everything mentioned here. Nothing worked. Then I moved jsonwebtoken dependency to the bottom of package.json ( Below my registy specific dependencies ).
Then it worked!
Spent 6 hours in fixing this. I feel so small now.
The docs explain how to control which files are not sent to the npm registry when you run npm publish.
If you use .npmignore, or you're not using git that set of files differs from the set that are pushed to your source repo.
Is there a way to list the files that npm publish will send?
I know that npm pack will create a tarball that contains those files, but creating a tarball and then listing its contents seems a little clunky.
Currently, there's no such thing in npm (see this issue).
At the moment you can use some external tools that implement the functionality you're asking for, e.g. pkgfiles or irish-pub.
As of at least npm#6, you can run npm publish --dry-run to see what files are included in your package.
https://docs.npmjs.com/cli/v6/commands/npm-publish