-
-
Notifications
You must be signed in to change notification settings - Fork 27k
Figure out 2.x CodeSandbox story #5128
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
Comments
Hey, thanks for letting me know! I can set up a testing sandbox of our CRA v2 implementation on staging today or tomorrow. It would also be good to know when you're going to release exactly so we can have our side updated in time. If you're actually planning on releasing tomorrow I can try to get one on staging today 🙂. |
@Timer your call |
I feel confident about shipping to |
Working on CRA v2 support now. Hope to have something in the next hour. |
Great! We just shipped |
Here's the PR: codesandbox/codesandbox-client#1124 |
Punting this to 2.x since it's pretty much figured out and doesn't need to block immediate 2.0.0 release. Let me know if you disagree. |
Sure |
I think we can close this one as we deployed v2 support: https://codesandbox.io/s/new |
Thanks! |
cc @CompuIves we're getting really close to releasing 2.0.0 of
react-scripts
, how can we make sure it works great on CodeSandbox?The text was updated successfully, but these errors were encountered: