I am installing Ghost and while installing it I followed the following steps at:
http://docs.ghost.org/installation/linux/
But on running npm start I get the following errors:
> node index
Bus error (core dumped)
npm ERR! weird error 135
npm ERR! not ok code 0
What should I do? I am a newbie to node or npm
According to this site, and this also, there is most likely an environment issue such as an improperly or missing file or configuration setting. Trying in a new, fresh installed environment should fix this issue.
Related
I have been trying to make a vite project as well as install some packages into some already existing projects in vscode yet when I do this I get the error of:
npm ERR! code EHOSTUNREACH
npm ERR! syscall connect
npm ERR! errno EHOSTUNREACH
npm ERR! request to https://registry.npmjs.org/create-vite failed, reason: connect EHOSTUNREACH 2606:4700::6810:1123:443
npm ERR! A complete log of this run can be found in:
npm ERR! /home/chimera/.npm/_logs/2022-11-12T23_58_02_327Z-debug-0.log
I have no idea how to fix this and it is quite annoying as I am not able to make or change any projects ): I also have tried searching this on StackOverflow and I get a similar error but none of the fixes I have tried seems to do anything. If you know how to solve this could you please explain why this happened ): I am also finding and I don't know if this is related to it or not that my terminals take forever to load when before when I opened one they took less than a second to do so? Also, I am using Ubuntu (The latest version) and previously just used the latest version of node and there is where I got the error, the moment I downgraded to node v16 it went away. The command I tried running was the command for creating a new react project and also to adding daisyui to a project I had.
Sorry for the following wall of text.
So I've been using someone else's meteor app. (they open sourced it) It's currently un-built and I've been running it on dev-mode. It's a lot slower than expected and users are having issues connecting to my local machine. So I'm attempting to deploy the app by following: https://guide.meteor.com/deployment.html#deploying.
So I've been getting errors when trying to run npm i. My dad recommended me to run npm cache verify and try again, then npm cache clean as a last resort. Neither worked and I've still am getting errors. Although as soon as I tried again after running npm cache verify the error amount skyrocketed. I unfortunately don't have the errors I got before I cleared my cache but I have the current logs here: https://pastebin.com/dAcRnE9v But here is a snapshot:
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! fibers#2.0.2 install: `node build.js || nodejs build.js`
npm ERR! Exit status 1
npm ERR! Failed at the fibers#2.0.2 install script.
I honestly don't have any idea what todo. I've never worked with meteor before, nor the fibers module that's failing. I don't even know if this is the right place I should be asking for help.
I once had fibers npm package in my package.json which caused a similar error. Once I removed it everything built just fine.
You can't change Meteor's version of node - for compatibility reasons it bundles node/npm with Meteor to protect you. Just prefix all your npm/node commands with meteor like this:
meteor npm install
It won't use the node version (13.x) that you have installed
I'm trying to install React through command prompt. NodeJS is already installed.
When I try to run this command:
npm i -g create-react-app
It is displaying error as shown below:
npm ERR! code ENOVERSIONS
npm ERR! No valid versions available for undefined
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\xyz\AppData\Roaming\npm-cache\_logs\2019-12-10T10_51_39_2222-debug.log
Sometimes this can happen when you are using a private NPM registry / proxy registry and it has corrupted metadata. I've seen this happen with Sonatype Nexus 3 - there were corresponding error messages in the server logs.
Are you sure you have the right Node version? Try updating NodeJS or try running: npx create-react-app my-app
you should check this out issue.
If the problem still exist, please check your versions with this:
npm -v
node -v
For me this error came up because I had a version number that did not exist for a package I wanted.
I am getting an error on creating my first react native app.
I am using following guide -
https://facebook.github.io/react-native/docs/getting-started.html
https://github.com/react-community/create-react-native-app
$ npm install -g create-react-native-app
--Worked fine
$ create-react-native-app my-first-native-app
--app created without errors
$ npm start
--gives error
Error: React native is not installed. Please run `npm install` in your project directory.
1:09:05: Error starting packager: Error: Couldn't start project. Please fix the errors and restart the project.
at C:\xdl\src\Project.js:1329:11
at Generator.next (<anonymous>)
at step (C:\reactJs-projects\my-first-native-app\node_modules\xdl\build\Project.js:1735:191)
at C:\reactJs-projects\my-first-native-app\node_modules\xdl\build\Project.js:1735:361
at <anonymous>
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! my-first-native-app#0.1.0 start: `react-native-scripts start`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the my-first-native-app#0.1.0 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
Tried fixing with downgrading npm to version 4 as recommended all over that version 5 has bugs.
npm i -g npm#4
I have also tried latest npm but neither of them worked.
When I run npm install on my project directory, instead of installing/updating my packages, it is giving following error
npm ERR! cb() never called!
npm ERR! This is an error with npm itself. Please report this error at:
npm ERR! <https://github.com/npm/npm/issues>
I see all dependencies downloaded in node_modules though
Any suggestion on what I have missed?
What I also noticed is when the app is created (using create-react-native-app my-first-native-app) it also added following error in console
yarn install v0.21.3
[1/4] Resolving packages...
warning jest-expo > jest > jest-cli > istanbul-api > istanbul-lib-hook#1.2.1: 1.2.0 should have been a major version bump
[2/4] Fetching packages...
error An unexpected error occurred: "https://registry.yarnpkg.com/react-native-web-maps/-/react-native-web-maps-
0.1.0.tgz: invalid tar file".
info If you think this is a bug, please open a bug report with the information provided in "C:\\reactJs-projects
\\MyNewNativeApp\\yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
Failed to install
Thank You!
Reinstall your NPM/YARN and get the newest version of React Native i have this problem too
after create your project with
$ create-react-native-app my-first-native-app
after you should enter your project folder :
$ cd my-first-native-app
and then open emulator or connect to tour device and run with
$ npm start
or
$ react-native run-android
pay attention you had installed android-SDK and android-JDK and your emulator is running
After trying different versions, I ended up using yarn and it worked on first instance. If anyone struggles with similar problem, then I would recommend using Yarn and move on. One can switch back to npm after the app is created. This is very common issue reported and for many developers it works with certain version.
Create new project using command : npx react-native init ProjectName
Create new project using particular version of react native :
npx react-native init ProjectName --version X.XX.X
After that go to project location
cd ProjectName
Run application on android platform
npx react-native run-android
I made an app using Node and am trying to host it using AWS's Elastic Beanstalk, but it always fails npm install when it reaches node-sass. Here is the error from the logs:
5162 error node-sass#4.5.0 postinstall: node scripts/build.js
5162 error Exit status 1
5163 error Failed at the node-sass#4.5.0 postinstall script 'node scripts/build.js'.
5163 error Make sure you have the latest version of node.js and npm installed.
5163 error If you do, this is most likely a problem with the node-sass package,
5163 error not with npm itself.
5163 error Tell the author that this fails on your system:
5163 error node scripts/build.js
5163 error You can get information on how to open an issue for this project with:
5163 error npm bugs node-sass
5163 error Or if that isn't available, you can get their info via:
5163 error npm owner ls node-sass
5163 error There is likely additional logging output above.
5164 verbose exit [ 1, true ]
And here is my repository: https://github.com/Jacob-Elder/react-socket.io-messaging
This is my aws configuration
I searched this issue and found some people reinstalled node-sass with the '--unsafe-perm' flag, but this doesn't seem to be a permissions issue. I'm new to AWS and coding so any help is much appreciated!
So I also had npm install fail on node-sass. I get roughly the same error message as you, but then a few lines above the lines you mention in the original post, I see this "make: g++: Command not found
make: *** [Release/obj.target/libsass/src/libsass/src/ast.o] Error 127".
Judging from this similar stackexchange post: https://serverfault.com/questions/204893/aws-ec2-and-build-essential,
which in turn points to the AWS docs, you may have to run sudo yum groupinstall "Development Tools" to get some additional binaries