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
Related
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
I’m getting that message after installing express globally.
I went through most of the solutions related to the /.bash_profile file and about exporting the correct PATH, but it still nothing works.
I tried this solution https://superuser.com/a/1081802 and it worked on the terminal, but when I close it and tried to execute the command express followed by the file I wanted to use, it ended up showing the same message.
Please help!
So I was looking for other kinds of solutions, and I remembered that I installed via the website and not by home-brew. Just in case, I uninstalled it and installed node again.
I run this:
npm install express -g
npm install express-generator -g
And up to this point it is now working.
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
Upon executing the following command:
npm install #angular/animations#'^5.2.0' #angular/common#'^5.2.0' #angular/compiler#'^5.2.0' #angular/compiler-cli#'^5.2.0' #angular/core#'^5.2.0' #angular/forms#'^5.2.0' #angular/http#'^5.2.0' #angular/platform-browser#'^5.2.0' #angular/platform-browser-dynamic#'^5.2.0' #angular/platform-server#'^5.2.0' #angular/router#'^5.2.0' typescript#2.4.2 rxjs#'^5.5.2'
I get messages saying that no compatible version of found for rxjs. Then when I remove the specific version, it says no compatible version is found for angular/animations. Then angular/common. Etc etc.
I'm pretty sure these versions are valid, since they're the ones recommend by this Angular upgrade tool (https://angular-update-guide.firebaseapp.com/) and I can also see the "valid install target" list, which includes the versions I'm trying to install.
I know our project's dependencies are in some special repository somewhere (Artifactory, I think?) so maybe this is happening because these versions are not in the repo NPM is looking at.
Is there a way to fix this for testing purposes before committing to having to install the new versions in the repo? In other words, how do I point NPM at the NPM repo rather than the company's repo?
Well, the answer I was looking for was here:
How to specify registry while doing npm install with git remote url?
However that didn't actually work.
The problem was simply a syntax issue. After I removed all the quotes from my command so it looked like the following command, it worked
npm install #angular/animations#^5.2.0 #angular/common#^5.2.0 #angular/compiler#^5.2.0 #angular/compiler-cli#^5.2.0 #angular/core#^5.2.0 #angular/forms#^5.2.0 #angular/http#^5.2.0 #angular/platform-browser#^5.2.0 #angular/platform-browser-dynamic#^5.2.0 #angular/platform-server#^5.2.0 #angular/router#^5.2.0 typescript#2.4.2 rxjs#^5.5.2
I am getting crazy with the node npm pathwatcher on FreeBSD-10-2.
I tried this with node 0.10.40, 0.12.x, 4.2.x but none worked
Just simple
npm install pathwatcher
then small test script
var p = require('pathwatcher')
What ever release of pathwatcher I choose (6.2.5 (latest), 4.1.0, 5.0.1) I get the errors (depend on release and node)
1. node_modules/pathwatcher/build/Release/pathwatcher.node: Undefined symbol "_Z12PlatformInitv"
2. module "pathwatcher" not found
The npm installation runs in any case without any error.
If I do the same on Debian/Ubuntu/MacOSX no problem.
What makes it special on BSD
Thanks or help
A long answer short :-)
After having this discussion thread on freebsd forum at:
https://forums.freebsd.org/threads/npm-pathwatcher-module-for-meteor-fails.53843/#post-302921
I created an update PR and that gots already merged
https://github.com/atom/node-pathwatcher/pull/95
So just use
npm install pathwatcher#6.3.0
Everythings works by now :-)