I tried installing react app with vite and after installation when i tried using npm run dev it keeps throwing this error,
dyld: Symbol not found: _clock_gettime
Referenced from: /Users/KELVIN/Desktop/ZZZ/react/mobile_banking/node_modules/#esbuild/darwin-x64/bin/esbuild
Expected in: flat namespace
failed to load config from /Users/KELVIN/Desktop/ZZZ/react/mobile_banking/vite.config.js
error when starting dev server:
Error: The service was stopped
at /Users/KELVIN/Desktop/ZZZ/react/mobile_banking/node_modules/esbuild/lib/main.js:1145:25
at Object.responseCallbacks.<computed> (/Users/KELVIN/Desktop/ZZZ/react/mobile_banking/node_modules/esbuild/lib/main.js:
701:9)
at Socket.afterClose (/Users/KELVIN/Desktop/ZZZ/react/mobile_banking/node_modules/esbuild/lib/main.js:691:28)
at Socket.emit (events.js:412:35)
at endReadableNT (internal/streams/readable.js:1333:12)
at processTicksAndRejections (internal/process/task_queues.js:82:21)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! mobile_banking#0.0.0 dev: `vite`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the mobile_banking#0.0.0 dev script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
please what can i do.
I've tried deleting the package.json and package-lock.json and installing it back using npm install but it still won't work.
Related
I'm updating a 3 years ago ruby on rails and react project trying to npm install but im stuck here getting this error
$ npm install
gyp: Undefined variable standalone_static_library in binding.gyp while trying to load binding.gyp
gyp ERR! configure error
gyp ERR! stack Error: `gyp` failed with exit code: 1
$ npm start
sh: node-sass-chokidar: command not found
npm ERR! code ELIFECYCLE
npm ERR! syscall spawn
npm ERR! file sh
npm ERR! errno ENOENT
npm ERR! frontend#0.1.0 build-css: `node-sass-chokidar src/styles -o src/styles`
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the frontend#0.1.0 build-css script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
I tried removing node_modules, update node version and npm version.
For me this issue happened with NodeJS 19 (specifically 19.2.0)
The issue is fixed when I reverted to NodeJS 18; aka NodeJS LTS
NodeJS LTS = Long Term Support; "recommended for most users" - which at the time of this writing (12/9/2022) is NodeJS 18.12.1
It seems like this issue (Undefined variable standalone_static_library...) may happen because:
node 19.0.0 has been changed to make process.config read only #43627
After reverting, it may still be mentioned as a warning, but not an error:
npm ERR! (node:7120) [DEP0150] DeprecationWarning: Setting process.config is deprecated. In the future the property will be read-only.
And while we're talking about versions, be careful about Python3 vs Python2!
npm ERR! gyp verb which failed Error: not found: python2
im useing the latest version of electron forge to make my app, so to make sure that the setup worked i ran the make command and it didn't work.
error:
PS D:\javascript\testing\New folder> cd my-app
PS D:\javascript\testing\New folder\my-app> npm run make
my-app#1.0.0 make D:\javascript\testing\New folder\my-app
electron-forge make
✔ Checking your system
✔ Resolving Forge Config
An unhandled rejection has occurred inside Forge:
Error: Could not find module with name: #electron-forge/maker-squirrel. Make sure it's listed in the
devDependencies of your package.json
at _default (D:\javascript\testing\New folder\my-app\node_modules#electron-forge\core\src\api\make.ts:132:15)
at D:\javascript\testing\New folder\my-app\node_modules#electron-forge\cli\src\electron-forge-make.ts:44:5
Electron Forge was terminated. Location:
{}
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! my-app#1.0.0 make: electron-forge make
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the my-app#1.0.0 make 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! C:\Users\nycas\AppData\Roaming\npm-cache_logs\2021-09-04T01_06_58_366Z-debug.log
PS D:\javascript\testing\New folder\my-app>
i have #electron-forge/maker-squirrel and its a brand new project that I literally just made
help is appreciated.
I am trying to setup react in my PC. I have completed downloading the reacr modules and am starting to run through local server and these errors occur to me.
events.js:167
throw er; // Unhandled 'error' event
^
Error: spawn cmd ENOENT
at Process.ChildProcess._handle.onexit (internal/child_process.js:232:19)
at onErrorNT (internal/child_process.js:407:16)
at process._tickCallback (internal/process/next_tick.js:63:19)
Emitted 'error' event at:
at Process.ChildProcess._handle.onexit (internal/child_process.js:238:12)
at onErrorNT (internal/child_process.js:407:16)
at process._tickCallback (internal/process/next_tick.js:63:19)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! portfolio#0.1.0 start: `react-scripts start`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the portfolio#0.1.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! C:\Users\mohin\AppData\Roaming\npm-cache\_logs\2020-03-18T05_50_06_309Z-debug.log
I know it's simple error for local server and tried to open the index.html file manually then it didnot show the react logo but instead showed something like this.
Please help me through the installation.
npm install error
It was due to inconsistency in npm versions I guess. I had deleted node modules and re-installed all the modules again using npm-install.
It worked fine from then.
I met this problem when execute the npm install module-name --save
It fails no matter what I install.
And it fails if I specified it in the package.json . and then run the npm install for the whole project.
There are some similar question posted like
NPM doesn't install any modules: network socket hangs up
NodeJS - What does "socket hang up" actually mean?
but unfortunately, it doesn't work for me. Also, npm install is OK with my other projects.
My environment: npm v6.4.1, node.js v10.10.0 serverless v1.28.0
Appreciated for the help of any kinds.
Here is my log message in my console:
> spawn-sync#1.0.15 postinstall /Users/pro/node_modules/spawn-sync
> node postinstall
> serverless#1.28.0 postinstall /Users/pro/node_modules/serverless
> node ./scripts/postinstall.js
Error: socket hang up
at createHangUpError (_http_client.js:322:15)
at TLSSocket.socketOnEnd (_http_client.js:425:23)
at TLSSocket.emit (events.js:187:15)
at TLSSocket.EventEmitter.emit (domain.js:442:20)
at endReadableNT (_stream_readable.js:1092:12)
at process._tickCallback (internal/process/next_tick.js:63:19)
npm WARN cognito-backend#1.0.0 No description
npm WARN cognito-backend#1.0.0 No repository field.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! serverless#1.28.0 postinstall: `node ./scripts/postinstall.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the serverless#1.28.0 postinstall 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:
I found a github issue that solves my problem:
https://github.com/maciejtreder/ng-toolkit/issues/448
use nvm install v10.6.0
Windows 10
node v8.9.2
npm 5.5.1
installed vue-cli through the use of npm but entering 'npm run dev' resulted in an error.
this is error message
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! webpack-simple#1.0.0 dev: `cross-env NODE_ENV=development webpack-dev-server --open --hot`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the webpack-simple#1.0.0 dev 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! C:\Users\hansol\AppData\Roaming\npm-cache\_logs\2017-12-08T04_14_50_859Z-debug.log
It appears as though you havent installed the node modules / dependencies.
Please try and run a
npm install
And see if that works
I used to face this problem when the port is busy.
So confirm the port you are opening for the dev server.
you can also change the port using a flag "--port 3000".