I will try to give as much information as possible on my problem, however part of the problem is that it prevents me from seeing everything that went wrong.
First of all, when I installed generator-gulp-bootstrap, it gave me a bunch of peer dependency warnings, but yeoman itself appeared to install fine, and they were just warnings, not actual errors.
Then, when i try to start a new bootstrap project in yeoman yo gulp-bootstrap it downloads a ridiculous amount of files (88.5mb)-- which is where I became concerned because no npm install has ever taken this long or downloaded this many files. I kept seeing warnings pop up as it was scrolling by, they looked like deprecation warnings, but they flew by too fast to be sure. I figured I would just go back and double check on them when it was finished, but that's when I noticed my biggest problem -- it doesn't let me scroll up very far. It doesn't even scroll past the top of the file structure map that it shows when a package is done installing. So from there I went to the npm-debug.log to try and find what went wrong, but I noticed it's 12,363 lines long -- and I have no idea where to look, and I don't know if I can even post that many characters in a post here.
I only really have 1 thing to go off - the one visible error at the bottom of the install, it won't let me scroll up far enough in my terminal to see what else went wrong, and I have no idea where to look in the debug log. I don't think I should post the debug log here because its 12.3k lines long....anyone have any idea what I should do from here? Thanks. I have tried removing all yeoman components and completely reinstalling yeoman, as well as the generators, and also reinstalled node-sass. Not sure what else to do now.
58576 error Windows_NT 6.1.7601
58577 error argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\Elliot\\AppData\\Roaming\\npm\\node_modules\\npm\\bin\\npm-cli.js" "install"
58578 error node v4.1.1
58579 error npm v3.3.5
58580 error code ELIFECYCLE
58581 error node-sass#0.9.6 install: `node build.js`
58581 error Exit status 1
58582 error Failed at the node-sass#0.9.6 install script 'node build.js'.
58582 error This is most likely a problem with the node-sass package,
58582 error not with npm itself.
58582 error Tell the author that this fails on your system:
58582 error node build.js
58582 error You can get their info via:
58582 error npm owner ls node-sass
58582 error There is likely additional logging output above.
You should open a bug report:
Failed at the node-sass#0.9.6 install script 'node build.js'.
This is most likely a problem with the node-sass package
It might be that you don't have a compatible C compiler on your machine, or maybe the node-sass build is broken for windows.
In the meantime, just try the usual debugging npm installation issue:
At this point I'd make sure npm and node are on the latest version.
Then I'd try to only run npm install node-sass.
Related
at some point I got an error after each npm install. Says something about gyp error but I have no idea how to fix it. That package was working with the old node version. I've tried to remove manually node and install it again but doesn't seem to work (or maybe I'm not doing it properly...)
Log:
https://pastebin.com/crzWVwJn
Parcel was the problem. I'm not going to use it anymore so I removed it. But first I've tried to update to last version and same problem with the lmdb-store dependency.
I have been trying for sometime already to just run "npm start" for an old app developed with EmberJs but I get several errors. I had tried the following:
Uninstall, cache clean, install Ember-cli
Remove the "node_modules" and run "npm install"
Updating ember-cli-babel
And some few others like updating / removing packages
I haven't open this project for around 3 years so I am pretty sure there are new updates that probably I need to follow but not sure what else to do after the list I just mentioned above.
I uploaded what I get when running "npm start".
Any guidance, help, or suggestion I would appreciate it! Thanks in advance!!
user#User-MacBook-Air app2 % npm start
> app#0.0.0 start /Users/user/Projects/app2
> ember serve
DEPRECATION: ember-cli-babel 5.x has been deprecated. Please upgrade to at least ember-cli-babel 6.6. Version 5.2.8 located: app -> ember-clean-tmp -> ember-cli-babel
ember-cli-htmlbars-inline-precompile v1.0.0 and above require the ember-cli-babel v6.7.1 or above. To use ember-cli-babel v5.x please downgrade ember-cli-htmlbars-inline-precompile to v0.3.
An error occurred in the constructor for ember-cli-htmlbars-inline-precompile at /Users/user/Projects/app2/node_modules/ember-cli-htmlbars-inline-precompile
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! app#0.0.0 start: `ember serve`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the app#0.0.0 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /Users/user/.npm/_logs/2022-04-17T17_03_00_039Z-debug.log
To make your life easier and get your app going faster, I’d suggest trying to stay in the Babel 5.x world and see how few dependencies you can update to start with. So I’d probably start by heading the suggestion in the warning and downgrade
ember-cli-htmlbars-inline-precompile v1.0.0 and above require the
ember-cli-babel v6.7.1 or above. To use ember-cli-babel v5.x please
downgrade ember-cli-htmlbars-inline-precompile to v0.3.
That may still mean you but other errors, but ideally you’d stick with the same ember, ember cli and ember data (and all associated dependencies) instead of trying to do a large and possibly time-consuming upgrade
Also, might be worth introducing a lock file (either using Yarn 1 or a Node 6 lock file if your system can run with it) so you don’t hit this issue in the future.
I updated my version in package.json and ran "npm publish". I did not see any error and see the log "package-name prepublishOnly" in terminal. Now if I go to https://www.npmjs.com/package/, I could not see updated package. Then if I ran "npm publish" again, it gives me error as below:
npm ERR! publish Failed PUT 403
npm ERR! code E403
npm ERR! Forbidden The feed already contains the package 'package-name' at version 'X.Y.Z': 'package-name'
I would like to know why and if I publish the package successfully or not.
Give it some time. Your package is probably uploaded, the webpage might not be updated immediately yet.
I thought I was seeing the same thing with my package as of 11:38AM PT on 2/28/2019, as the page of my package would show the older version. However, when searching for my package I would see the new version. Most importantly, running npm init and npm install mypackage would install the new version, which is what matters the most anyway.
I'm having some issues uninstalling some of my global npm packages, in that they don't appear to be fully removing.
As an example, I've been trying to remove the beta Angular CLI package (as this package was renamed for its 1.0.0 release). Running npm uninstall -g angular-cli appears to work, however when I then run npm list -g --depth=0 the package appears to remain in the list, now with an error:
error: ENOENT: no such file or directory, open '/usr/local/lib/node_modules/angular-cli/package.json
It appears as though the package has not been fully removed - I'm not sure if this can be fixed using npm prune, or simply by going in and manually deleting any files that may be left over.
I've not had any success googling around the issue, however this could be because I'm not entirely sure what to search for, as evidenced by my not-so-eloquently worded title for this question.
If anyone has any thoughts, I'd be very grateful to hear them!
When I do npm list --global, one package, phonegap, shows as invalid.
npm ERR! invalid: phonegap#5.0.0-0.28.1 /usr/local/lib/node_modules/phonegap
No other packages have any errors or problems. I’ve tried to look into this, and learned that the message means a dependency is unfulfilled, but I can’t figure out which one. If I run npm update --global phonegap it exits cleanly, with no errors.
I originally installed npm & node via Homebrew, if that’s relevant. Here’s my full list of globally installed packages.
How do I diagnose this?
Have you tried changing the permissions for that package? I recently had a similar problem with global packages and it turned out to be a permissions issue
https://docs.npmjs.com/getting-started/fixing-npm-permissions