Cannot start npm after installing react ERR! react-scripts start - redux

While using redux with react. I was trying to do npm start for my app(reactwithredux) after installing react-redux and redux libraries . I see this error below. I'm trying to figure it out myself, but no luck so far. Please help me out.
'react-scripts' is not recognized as an internal or external command,
operable program or batch file. npm ERR! code ELIFECYCLE npm ERR!
errno 1 npm ERR! reactwithredux#0.1.0 start: react-scripts start npm
ERR! Exit status 1 npm ERR! npm ERR! Failed at the
reactwithredux#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\preet\AppData\Roaming\npm-cache_logs\2018-09-21T01_19_43_724Z-debug.log

Try following
npm run cache clean --force
rm -rf node_modules (in project
directory)
npm install
If this doesn't solve the error, please provide a link to repo need to take a look at package.json.

Related

I get multiple errors, when I try to install all modules from a package.json file on my nginx webserver

I'm currently trying to configure my portfolio on a VPS using nginx and Putty.
Now I want to install all required modules for my backend, but I get this errors.
I have no idea what to do and would love to get some help.
npm ERR! Linux 4.15.0
npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "install"
npm ERR! node v8.10.0
npm ERR! npm v3.5.2
npm ERR! path /root/portfolio/server/node_modules/.staging/#types/webidl-conversions-b037bbf1/package.json
npm ERR! code ENOTDIR
npm ERR! errno -20
npm ERR! syscall open
npm ERR! ENOTDIR: not a directory, open '/root/portfolio/server/node_modules/.staging/#types/webidl-conversions-b037bbf1/package.json'
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR! <https://github.com/npm/npm/issues>
npm ERR! Please include the following file with any support request:
npm ERR! /root/portfolio/server/npm-debug.log
To install all the modules, I went to my backend folder and typed 'npm install' in my Putty console.
Then it starts to download the modules and everything seems fine, until the errors pop up after a few seconds.
I also tried 'apt-get update' and 'apt-get upgrade', but it changes nothing.
I found the solution to my problem.
I had to update my node and npm, but not like usually with 'apt update', 'apt upgrade', 'apt install nodejs' or 'apt install npm'.
Instead I tried this:
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.35.3/install.sh | bash
nvm install 14.4.0
... and then it worked.
Hope this will help someone

Firebase functions install failing due to auth

I keep trying to npm install firebase functions. I've done this many times before and this is the first time I am getting this issue. The error is as follows:
PS C:\Users\jacob\Desktop\sultvueweb> npm install firebase firebase/functions
npm ERR! Error while executing:
npm ERR! C:\Program Files\Git\cmd\git.EXE ls-remote -h -t ssh://git#github.com/firebase/functions.git
npm ERR!
npm ERR! Host key verification failed.
npm ERR! fatal: Could not read from remote repository.
npm ERR!
npm ERR! Please make sure you have the correct access rights
npm ERR! and the repository exists.
npm ERR!
npm ERR! exited with error code: 128
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\jacob\AppData\Roaming\npm-cache\_logs\2020-04-28T22_58_26_800Z-debug.log
I can't seem to figure out where I need to update my credentials to make this work. Thank you for any help.
My issue was I didn't have an elevated command prompt in my text editor. I tried it in an admin prompt and worked right away. Not sure why it would have given the errors it did.

VMWare Clarity - master branch - `npm run angular:dev:start` fails with ERROR: Task not found: "'core:build:ts"

Unable to run dev mode of Clarity after checking out master.
Following error is reported.
λ npm run angular:dev:start
> #clr/clarity#3.0.0-next.8 angular:dev:start C:\Users\shrees3\Documents\clarity
> npm run core:build:src && ng serve dev
> #clr/clarity#3.0.0-next.8 core:build:src C:\Users\shrees3\Documents\clarity
> npm-run-all core:build:sass:components 'core:build:ts -- --force'
ERROR: Task not found: "'core:build:ts"
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! #clr/clarity#3.0.0-next.8 core:build:src: `npm-run-all core:build:sass:components 'core:build:ts -- --force'`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the #clr/clarity#3.0.0-next.8 core:build:src 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\shrees3\AppData\Roaming\npm-cache\_logs\2020-02-20T14_17_10_235Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! #clr/clarity#3.0.0-next.8 angular:dev:start: `npm run core:build:src && ng serve dev`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the #clr/clarity#3.0.0-next.8 angular:dev: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\shrees3\AppData\Roaming\npm-cache\_logs\2020-02-20T14_17_10_370Z-debug.log
Steps tried:
Clone Clarity and checkout master branch.
Run npm install
Run npm run angular:dev:start
Platform
Windows Laptpop
Using https://cmder.net/ Command Window which supports typical linux utilities.
Angular: 9.0.2
Node: 10.16.0
Clarity: "3.0.0-next.8"
The angular app depends on the core components.
Can you try running
npm run core:build
and then rerun
npm run angular:dev:start
Response from Clarity Team on Github issue:
This is a Windows specific issue with the handling of single quotes '. We don't actively develop on Windows so don't always catch these things. The quotes probably need to be escaped for Windows, unless you opt to use the Ubuntu shell.

Can't npm install firebase

I'm trying to do npm install for firebase but I keep running into errors...
I tried with npm version 5.6.0 and 5.7.1
I even tried installing assert-plus but that also failed (similar error to below). Any suggestions?
vagrant [polaris]> npm install firebase
npm ERR! path /vagrant/polaris/node_modules/grpc/node_modules/dashdash/node_modules/assert-plus/package.json.2882240414
npm ERR! code ENOENT
npm ERR! errno -2
npm ERR! syscall open
npm ERR! enoent ENOENT: no such file or directory, open '/vagrant/polaris/node_modules/grpc/node_modules/dashdash/node_modules/assert-plus/package.json.2882240414'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent
npm ERR! A complete log of this run can be found in:
npm ERR! /home/vagrant/.npm/_logs/2018-03-14T23_28_13_938Z-debug.log
You should use npm install -g firebase-tools instead of npm install -g firebase. After that, you'll be able to initialize your project on your PC.
One quick suggestion. Delete your node_modules folder and do a fresh 'npm install'.

npm run build error, no such file or directory, open 'build/bundle.css'

I'm attempting a routine-test of a customized WordPress-installation on a localhost production supported by the node package-manager. After instantiating the WordPress core-files, ensuring successful connection to the database and updating a few assets, I attempted to change-directory into the corresponding WordPress-theme files to run the node-package-manager install command with npm install (which was successful) and then attempted to execute the CSS-compiler with npm run buildas per routine; however, on this attempt, I encountered the following errors within my below terminal output:
vetsi npm run build
> # build /Users/alexsingleton/Sites/vetsi/wp-content/themes/vetsi
> npm-run-all --silent compile:css compile:js
/Users/alexsingleton/Sites/vetsi/wp-content/themes/vetsi/node_modules/stylus/bin/stylus:715
if (err) throw err;
^
Error: ENOENT: no such file or directory, open 'build/bundle.css'
at Error (native)
ERROR: compile:css: None-Zero Exit(1);
npm ERR! Darwin 16.4.0
npm ERR! argv "/Users/alexsingleton/.nvm/versions/node/v4.4.4/bin/node" "/Users/alexsingleton/.nvm/versions/node/v4.4.4/bin/npm" "run" "build"
npm ERR! node v4.4.4
npm ERR! npm v4.2.0
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! # build: `npm-run-all --silent compile:css compile:js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the # build script 'npm-run-all --silent compile:css compile:js'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! npm-run-all --silent compile:css compile:js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! /Users/alexsingleton/.npm/_logs/2017-02-15T17_48_20_907Z-debug.log
➜ vetsi
I've tried updating both the node package manager with npm install -g npm and verified the correct version corresponding to another successful localhost production with nvm ls generating the below output:
vetsi nvm ls
v0.12.7
-> v4.4.4
system
default -> 4.4.4 (-> v4.4.4)
node -> stable (-> v4.4.4) (default)
stable -> 4.4 (-> v4.4.4) (default)
iojs -> iojs- (-> N/A) (default)
➜ vetsi
Needless to say, the above-errors preclude any localhost pages from rendering, though I can successfully access and navigate within the WordPress Content Management system. I would appreciate any guidance- thank you!
After investigating the localhost-production within the console of Google Chrome Inspector Tools, the error reported that the entire node package-manager folder and dependencies were missing. Since neither npm-install nor npm build didn't instantiate the package-folder or dependencies, I simply copied the files from my other working localhost production, specifically bundle.css where it was apparently missing from the appropriate path (wp/themes/vetsi/build). For now, this hack is the best solution to my problem but I welcome alternative analysis or clarification as to why the aforementioned commands didn't correctly execute according to my previous successes. Thanks!

Resources