-
Notifications
You must be signed in to change notification settings - Fork 47.3k
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
CDN production version is broken #14765
Comments
At a quick glance, I think that line is referring to |
Changing Can you confirm that you're still seeing this issue? |
Do these two links work for you? https://unpkg.com/react@16.8.0/umd/react.production.min.js |
I think this issue highlights the fact that splitting the current owner/dispatcher refs (#14548) probably broke peer dependencies. 😦 Maybe we could do a bugfix release that patches backwards compat? |
Yes. My test is working again without changing anything. |
To be clear, an older version of the An older renderer will work with a newer version of the |
This specific issue was caused by a transient unpkg problem, so I'm going to close it. The backwards incompatibility this is covered by #14763 so let's track it there. |
Hi
This morning all of our sites which use React have stopped working. We use the CDN:
https://unpkg.com/react@16/umd/react.production.min.js
https://unpkg.com/react-dom@16/umd/react-dom.production.min.js
To reproduce download zip and run example from here:
https://reactjs.org/docs/add-react-to-a-website.html
The sites work with the development version but switching to the production version causes script error:
Workaround
Specify previous version:
https://unpkg.com/react@16.7.0/umd/react.production.min.js
https://unpkg.com/react-dom@16.7.0/umd/react-dom.production.min.js
Please advise
Thanks
Andrew
The text was updated successfully, but these errors were encountered: