Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

npm run eject silently fails when a config folder already exist

See original GitHub issue

Description

npm run eject silently fails when a config folder already exist.

Expected behavior

It’s a common behavior to have a /config folder at the base of a project. npm run eject should throw an error or even better, “merge” new files with existing ones.

Actual behavior

➜  react-starter git:(master) mkdir config
➜  react-starter git:(master) npm run eject

> react-scripts eject

Are you sure you want to eject? This action is permanent. [y/N]
y
Ejecting...
➜  react-starter git:(master)

Environment

node -v: 5.0.0 npm -v: 3.3.6 Operating system: macOS Sierra

Reproducible Demo

Clone the repo
mkdir config
npm run eject

Thanks 🙏

Issue Analytics

State:
Created 7 years ago
Comments:7 (3 by maintainers)

Top GitHub Comments

1reaction

ugogocommented, Nov 18, 2016

> react-scripts eject

Are you sure you want to eject? This action is permanent. [y/N]
y
Ejecting...
`config` already exists in your app folder. We cannot continue as you would lose all the changes in that file or directory. Please move or delete it (maybe make a copy for backup) and run this command again.

npm ERR! Darwin 16.1.0
…

All’s good, thanks 👍

0reactions

moffsugitacommented, Oct 25, 2018

Me too where is the file?? config already exists in your app folder.