-
-
Notifications
You must be signed in to change notification settings - Fork 26.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve npm run eject
description
#363
Conversation
I feel as if the description for `npm run eject` is incredibly vague. `eject` does more than just removing the tool and that should be explained to the user.
Improve `npm run eject` description
Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. In order for us to review and merge your code, please sign up at https://code.facebook.com/cla - and if you have received this in error or have any questions, please drop us a line at cla@fb.com. Thanks! |
Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Facebook open source project. Thanks! |
Can you show the screenshot? If this doesn't look very well we should just reformat the whole message. We can use chalk inversion to highlight commands, and write small descriptions below. |
@gaearon screenshots supplied. Looks OK. Sorry for the massive images! |
I don’t like that I was thinking something like
Where all commands ( What do you think? |
@gaearon sounds good to me, I'll have some time Monday to implement this. 👍 |
@gaearon I've committed the changes that add better formatting and highlighting. Unfortunately, I've generated a node-debug log that I can't seem to get rid of 😦 |
@btnwtn You can get rid of the npm-debug.log file with
Alternatively you can also remove it directly from the GitHub web interface, if you go to https://github.com/btnwtn/create-react-app/blob/master/npm-debug.log and click the thrash can icon. |
console.log(' Bundles the app into static files for production.'); | ||
console.log(); | ||
console.log(chalk.cyan('npm run eject')); | ||
console.log(' Removes this tool and copies build dependencies, configs, and scripts into the app directory.') |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Deleted npm-debug.log and fit npm script descriptions to 80 characters. Looks good to me 😄 |
Thanks @btnwtn! Can you also merge create-react-app master branch into yours to resolve the conflicts. Happy to merge as soon as that's done. |
Having issues with git... Can't figure this out :\ |
With the HTTPS env var set 'true', the dev server will serve over HTTPS.
* Clarify proxy instructions in generated app README * Add backticks to format text/html as code
For the 0.4.0 CHANGELOG entry, the npm install command should be: ``` npm install --save-dev --save-exact react-scripts@0.4.0 ``` Not: ``` npm install --save-dev --save-exact react-scripts@0.3.1 ```
* Change http-proxy-middleware logLevel from silent to error * provide onError handler for httpProxyMiddleware
* Adds JSX extension support * PR changes * Add testRegex * Add note about not recommending JSX, link to issue
…dleware. (#588) * Change http-proxy-middleware logLevel from silent to error * provide onError handler for httpProxyMiddleware * Send proper error reponse upon proxy error.
* Warn about unsupported Node.js versions Add the `engines` field to package.json so users of old Node.js versions will at least get a warning when trying to install create-react-app or react-scripts, e.g.: npm WARN engine create-react-app@0.3.0: wanted: {"node":">=6"} (current: {"node":"4.2.3","npm":"2.14.7"}) * Remove duplicated field and extra whitespace * Change the engine version back to 4
The regexes in the Jest `moduleNameMapper` configs were a bit too strict, causing them to not pick up files with special characters like `@` in the file path. Change them to match anything with the correct file extension.
…with docker node (#620) * Specify cache directory for babel loader * Use `react-scripts` for folder name instead
Resolves an issue that can occur in certain situations that causes a build error when user has CDed into an incorrectly cased directory.
Oh for fucks sake. I'm going to close this, re-fork, and open a new pull request. @fson |
I feel as if the description for
npm run eject
is incredibly vague.eject
does more than just removing the tool and that should be explained to the user.