-
-
Notifications
You must be signed in to change notification settings - Fork 26.9k
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
Syntax error crashes app on Internet Explorer 11 in development #2691
Comments
This makes total sense, thanks for flagging. Want to send a PR to downgrade |
Definitely! I'll try to do that shortly 👍 |
Please verify this release fixes it. |
Yep, that takes care of it. Thank you! |
To anyone who ends up here still having problems, I found success using babel-engine-plugin to transpile the necessary node_modules for ie11. |
Is this a bug report?
Yes
Can you also reproduce the problem with npm 4.x?
Yes
Which terms did you search for in User Guide?
"internet explorer 11", "syntax error"
Environment
node -v
: 8.1.2npm -v
: 5.0.3yarn --version
(if you use Yarn): 0.24.5npm ls react-scripts
(if you haven’t ejected): 1.0.9Then, specify:
Steps to Reproduce
npm i -g create-react-app
create-react-app my-app
cd my-app
npm start
Expected Behavior
I expected the app to load successfully and to show the initial Create React App page, like normal.
Actual Behavior
A blank white screen shows instead and a syntax error is thrown in the console.
Reproducible Demo
I don't have an easily reproducible demo, but found that you really just need the basic initial steps from CRA's documentation.
I first encountered this working on an app for my company that's not using CRA, but is using
react-dev-utils
. When I removereact-dev-utils/webpackHotDevClient
from our wepack entry array, the app loads successfully as expected. I primarily use Chrome for development, but just happened to run into this during one of my compatibility check-ins on IE 11.As far as I can tell, the issue seems to be a result of this set of dependency updates. Specifically, the update of
strip-ansi
to4.0.0
seems to also updateansi-regex
to3.0.0
which started exporting an arrow function instead of a regular function in this commit. Since IE 11 doesn't support arrow functions, I imagine this might be the problem, or at least related?The text was updated successfully, but these errors were encountered: