Lately there's been a lot of weird things going on when I go to create a new React App using create-react-app . This is either done through npm start not activating, yarn not being initiated with Yarn Start or whatever else the problems list may give me.
I would do everything the terminal said like "delete package-lock.json" "delete NPM folder" and whatever else might be going on.
One solution I found for this is inside your NPM folder in your main computer directory is to delete the webpack folder. It's not the most ideal solution, but it seems to work for me. Until today.
Today was a whole whirlwind of issues. Not only did those issues continue to come up, but deleting my webpacks folder as I mentioned from NPM didn't help either. Now as far as I know, deleting NPM extensions from the root of your computer isn't going to hurt anything as it'll be rewritten when you run yarn or npm i or npm install. Good thing huh?
Anyways something I learned to fix this problem was to give the computer a good ol' restart. Shocker huh? Then follow along the steps it gives you again and it should work.
Another work around can be to run yarn install then yarn update. That can give your project a new life. I'm not sure why this is a solution as it should update at times for you, but giving it a kick in the butt seems to help too.
Top comments (19)
Sir,I 'm stuck at npx create-react-app please will you give me solution
Can you please specify what exactly your problem is? Any error messages?
Then I am sure someone can help you :)
[?25l[[7m [27m[90m......[0m] - postinstall:p-limit: [32minfo[0m [35mlifecycle[0m p-limit@1.3.0~posti[[7m [27m[90m......[0m] | postinstall:ansi-regex: [32minfo[0m [35mlifecycle[0m ansi-regex@2.1.1~posti[[7m [27m[90m......[0m] | postinstall:extend-shallow: [32minfo[0m [35mlifecycle[0m extend-shallow@2.0[[7m [27m[90m......[0m] | postinstall:has-value: [32minfo[0m [35mlifecycle[0m has-value@1.0.0~postins[[7m [27m[90m......[0m] | postinstall:asn1.js: [32minfo[0m [35mlifecycle[0m asn1.js@4.10.1~postinstal[[7m [27m[90m......[0m] | postinstall:os-browserify: [32minfo[0m [35mlifecycle[0m os-browserify@0.3.0[[7m [27m[90m......[0m] - postinstall:cssesc: [32minfo[0m [35mlifecycle[0m cssesc@2.0.0~postinstall: [[7m [27m[90m......[0m] | postinstall:regexpp: [32minfo[0m [35mlifecycle[0m regexpp@3.0.0~postinstall[[7m [27m[90m......[0m] | postinstall:string_decoder: [32minfo[0m [35mlifecycle[0m string_decoder@1.1[[7m [27m[90m......[0m] | postinstall:simple-swizzle: [32minfo[0m [35mlifecycle[0m simple-swizzle@0.2[[7m [27m[90m......[0m] - postinstall:@babel/highlight: [32minfo[0m [35mlifecycle[0m @babel/highlight[[7m [27m[90m......[0m] | postinstall:@babel/generator: [32minfo[0m [35mlifecycle[0m @babel/generator[[7m [27m[90m......[0m] - postinstall:send: [32minfo[0m [35mlifecycle[0m send@0.17.1~postinstall: sen[[7m [27m[90m......[0m] - postinstall:typedarray: [32minfo[0m [35mlifecycle[0m typedarray@0.0.6~posti[[7m [27m[90m......[0m] | postinstall:postcss-color-gray: [32minfo[0m [35mlifecycle[0m postcss-color-[[7m [27m[90m......[0m] - postinstall:schema-utils: [32minfo[0m [35mlifecycle[0m schema-utils@2.6.5~p[[7m [27m[90m......[0m] | postinstall:utila: [32minfo[0m [35mlifecycle[0m utila@0.4.0~postinstall: ut[[7m [27m[90m......[0m] | postinstall:cliui: [32minfo[0m [35mlifecycle[0m cliui@4.1.0~postinstall: cl[[7m [27m[90m......[0m] - postinstall:string-width: [32minfo[0m [35mlifecycle[0m string-width@3.1.0~p[[7m [27m[90m......[0m] - postinstall:pump: [32minfo[0m [35mlifecycle[0m pump@2.0.1~postinstall: pump[[7m [27m[90m......[0m] - postinstall:yaml: [32minfo[0m [35mlifecycle[0m yaml@1.8.3~postinstall: yaml[[7m [27m[90m......[0m] - postinstall:postcss-loader: [32minfo[0m [35mlifecycle[0m postcss-loader@3.0[[7m [27m[90m......[0m] / postinstall: [32minfo[0m [35mlifecycle[0m react-scripts@3.4.1~postinstall: [[7m [27m[90m......[0m] / postinstall: [32minfo[0m [35mlifecycle[0m react-scripts@3.4.1~postinstall: [[7m [27m[90m......[0m] / postinstall: [32minfo[0m [35mlifecycle[0m react-scripts@3.4.1~postinstall: [[7m [27m[90m......[0m] / postinstall: [32minfo[0m [35mlifecycle[0m react-scripts@3.4.1~postinstall: [[7m [27m[90m......[0m] \ postinstall: [32minfo[0m [35mlifecycle[0m react-scripts@3.4.1~postinstall: [[7m [27m[90m......[0m] \ postinstall: [32minfo[0m [35mlifecycle[0m react-scripts@3.4.1~postinstall: [[7m [27m[90m......[0m] / postinstall: [32minfo[0m [35mlifecycle[0m react-scripts@3.4.1~postinstall: [[7m [27m[90m......[0m] - postinstall: [32minfo[0m [35mlifecycle[0m react-scripts@3.4.1~postinstall: [[7m [27m[90m......[0m] - postinstall: [32minfo[0m [35mlifecycle[0m react-scripts@3.4.1~postinstall: [[7m [27m[90m......[0m] - postinstall: [32minfo[0m [35mlifecycle[0m react-scripts@3.4.1~postinstall: [[7m [27m[90m......[0m] - postinstall: [32minfo[0m [35mlifecycle[0m react-scripts@3.4.1~postinstall: [K[?25h+ cra-template@1.0.3
55 packages are looking for funding
run
npm fundfor detailsfound [92m0[0m vulnerabilities
[K[?25h7m
am getting this type of error when i create a new react app
I can't see an error withing this log but some lines inbetween are cut off by "...".
Could you please format it with three backticks at the beginning and again at the end so it's well formatted?
after that type of error only nodemodules,package-lock,package.json files are only created it is not creating the entire structure like src,public ..sir, please will you provide me the solution and how to solve it.
Can you please provide the error message?
core-js@2.6.11 postinstall D:\app2\node_modules\babel-runtime\node_modules\core-js
this was my error
I'm afraid but there is no error message. This is only the call stack.
I am also getting the same messages , I know there are no errors but the code is getting stuck at the line of npm audit fix .
It doesn't show anything after that
Which OS are you using? When on an Unix system, try to use
sudo.Otherwise try to delete your npm cache and try again.
I'm using windows 10
Same command, try
npm cache cleanand run your commands afterwards.Thanks for the suggestions but actually when i downloaded nodejs with 32 bits. It worked so thanks for ur time
Good you solved it 😊
Thank you so much
Hi, I'm facing the same problem, that it got stopped after npm audit fix. You did install nodejs for 32bit, but my system is 64 bit, what should I do ? Can you help me to figure it out.
I discovered
pnpmfor myself just recently and must say I'm very pleased with it and have no such problems since I switched to pnpm.📦🚀 Fast, disk space efficient package manager
pnpm
Features:
package.json.pnpm-lock.yaml.Like this project? Let people know with a tweet.
Table of Contents
Background
pnpm uses hard links and symlinks to save one version of a module only ever once on a disk When using npm or Yarn for example, if you have 100 projects using the same version of lodash, you will have 100 copies of lodash on disk. With pnpm, lodash will be saved in a single place on the disk and a hard link will put it into…
I am stuck at npm start
I’m having kinda the same problem with electron. And this is the first time I’ve used electron. So... so far so bad.