* mv create-react-app/index.js -> create-react-app/creteReactApp.js
* update to modern code style
* var -> cosnt
* set trailing-coma to es5 for prettier
* Add red box prototype
* Unmount fail node when hot-reloaded (future proofing)
* Slightly improve error reason
* Add Chrome unhandledrejection listener
* Close red box when Escape is pressed
* Construct our own source if not available
* Resolve sourcemaps for friendlier traces
* Allow error to be scrolled
* Only utilize sourcemaps, not the magic. :(
* Make view similar to React Native
* Fix an uncaught syntax error
* Add workaround for Firefox 50
* Add a hint for closing the prompt
* Multiple error support
When there's multiple errors, simply state that there are more instead of re-rendering
* Log any renderer error
* Dim node_modules in display
* Override chrome stack trace limit
* Magic: show me some source!
* Add ability to toggle internal calls
* Switch text from show -> hide
* Change color scheme to something easier on the eyes
* Change UI to be friendlier (thanks @nicinabox)
https://github.com/facebookincubator/create-react-app/pull/1101#issuecomment-263621057https://github.com/facebookincubator/create-react-app/pull/1101#issuecomment-263636171
* Update styles
* Add container inside overlay
* Apply pre style
* Add line highlight
* Add omitted frames ui
* Move yellow to var
* Do all function names in black
* Adapt container based on screen size
* Extract ansiHTML
Use base16-github theme
* Linting
* Add syntax highlighting of errors
* Linting
* Remove white background
* Append new files to package.json
* Target exact version
* White is a little harsh, use same color as red box.
* Fix a bug where omitted frames would never be rendered
(under certain circumstances)
* Show local file path instead of confusing webpack://
* Do not require the entire file
* Remove css file
* Use context size, not a magic variable.
* Fix title regression
* Update dependency
* Do not center text for internal calls
* Temporarily disable links
* Switch internal toggle to 'i'
* Remove unnecessary rules from container style
* Reduce omitted frames font size
* Fix font family in pre > code
* Re-introduce line highlighting
* Object.<anonymous> -> (anonymous function)
* Add ability to see script source
* Add missing ansi mappings
* Remove SIAF
* Skip native functions
* Extract hints div function
* Extract renderers
* Refacor var names
* If source is disabled, don't use the line.
* Allow toggle between source
* Allow bundles to be expanded
* Wow, how did I let this one slip?
* Toggle text for UX/DX
* Make it so clicking Close unmounts the error component
* Do not allow hot reloading once an error is thrown
* Do not wrap lines for small displays
* Fix toggle when additional errors happen
* Make the close a button
* Capture and store errors
* Dispose on render; move additional logic
* Only make code not wrap
* Switch to a view-by-index method
* Allow user to switch between errors with arrow keys
* Fix text while switching between errors
* Update close button style
* Render additional errors at top
* Add left and right arrows
* Make frames pointy
* UTF-8 arrows
* Don't mount unneeded DOM node
* Switch to single changing text for compiled <-> source
* Don't display arrows with only one error.
* Collapsed and expanded
* Make sure the last collapse toggle is appended
* Do not show the stack trace if it doesn't resolve to a file we wrote
* Style container with media queries
* Do not allow x overflow; break words by default.
* Trim off whitespace of lines
* Remove padding since it's not outer-most
* Add footer message
* Extract css file to JS
* Only inject the css when the overlay is up
* Extract red variable
* Remove env
* Update babel-code-frame
* Set force color to true
* Extract out collapse div logic
* Remove arrow field
* Insert a top collapse
* Make browser friendlier
* Absolutify ^
* Make arrows buttons
* Accessify
* Let there be ES5
* Pretty css
* Use forEach where we can ...
* Remove extracted loop
* Fix IE compatibility
* Capture React warnings
* Add source override via React output parsing
* Whoops, fix arguments to crash.
* es5-ify
* Re-enable e2e-install directory test
* Only rewrite line number if it was resolved and leaves a line at bottom
* Rename failFast to crashOverlay
* Disable console proxy
* Appease linter
* Appease more
* Add note for using CHOKIDAR_USEPOLLING in virtual machines to enable HMR
* Use br in react-scripts template README md
* Use br in md for new line breaks
* Update troubleshooting HMR to allow for VMs running Windows
* Fix up the instructions
Array.forEach is passed the following parameters:
currentValue
The current element being processed in the array.
index
The index of the current element being processed in the array.
array
- https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/forEach
console.log takes multiple arguments. We only want to print the first one, the actually message.
Use a 'BROWSER' environment variable with npm start to specify which
browser to open. if the value of 'BROWSER' is not valid executable file,
don't open any browser.
- Use “Chrome” instead of "Google Chrome", It will try to use current active browser.
otherwise, use default.
- If “Chrome”s aren’t running, will fallback to opn(url)
* Reuse empty tab on open chrome apple script
* Break find tab into function
* Use property to store found
* Fix minor issues that caused window to not get active
* Don't strip stack traces of evaluated webpack code
* Strip stack traces at the end of a string
because the last line doesn't always have a `\n` and `create-react-app` is leaving the last line of the stack traces present in the error messages
* code comment
* code comment
* add logging of existing port process on start
* Move port process wording in start command on to next line
* Color the named processes as cyan in terminal output
* Add handling for multiple processes on a part
- With the currently process filtering, if multiple processes are returned as running on port 3000, this command would fail. This splits apart the process IDing and the process naming, to support multiple processes.
- One curious thing about the bash command to get processes, is that it'll include browsers with a window open on localhost:3000. May want to reconsider that.
* Add process directory to existing port warning
- also moved terminal coloring up, when getting the process, to be able to distinguish the process command from the directory
* Change output color to all cyan, except "in"
* Rename getProcessNameOnPort -> getProcessForPort
- better reflects its broadened scope (both command and directory)
* Add checking if process is a CRA instance, to customize port running message
- moved from using package.json to a regex, for reliability
* Move getProcessForPort to react-dev-utils
- also allowed for breakdown of commands into helper methods
* Add documentation for getProcessForPort
* Add getProcessForPort to list of dev-scripts files
* Use app's package name when CRA app is running on another port
* Filter port process by those listening
- Removed the handling of multiple process IDs since you can filtering by listening process (and not have the browser in the list of processes)
- Trimmed the terminal outputs for better matching (process id) and better terminal output (directory of process)
* Update README on port helpers, to specify only one port returned
* Add ignore of stderr when executing process commands
- Make sure any potential errors don't leak to the user
Running `create-react-app` in a Docker container causes an unhandled rejection error in nodejs > 6.5 because the `opn` module tries to open a web browser in a system that doesn't have one. I figured this error could be safely ignored.
A previous commit renamed the apple script to open chrome from
`chrome.applescript` to `openChrome.applescript`. That created
a minor bug. Even when chrome was open with the client app,
`npm start` would open the client app in a new Safari tab on
macOS instead of re-using the open tab in chrome.
