-
Notifications
You must be signed in to change notification settings - Fork 240
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
[BUG] React 3.1.1 does is not reusing the shims v2 module correctly -- causing __extends errors #1553
Comments
I've deprecated v3.1.1 package until I can publish an updated version |
[BUG] React 3.1.1 does is not reusing the shims v2 module correctly -- causing __extends errors #1553 - Remove unnecessary shims import, fix packaging and tests
[BUG] React 3.1.1 does is not reusing the shims v2 module correctly -- causing __extends errors #1553 - Remove unnecessary shims import, fix packaging and tests
PR to fix this is #1555 |
[BUG] React 3.1.1 does is not reusing the shims v2 module correctly -- causing __extends errors #1553 - Remove unnecessary shims import, fix packaging and tests
Reopening for tracking |
FYI - Internal prod build servers are timing out -- I need a good clean run to be able to release, will release as soon as I get a good run. |
Still having issues with the new tests on the internal servers -- still working on it |
Finally got a good build, however, the publish step is broken and will require an update -- unlike to get this fixed today now 😞 😭 |
Publish step is broken |
Got socket timeout issue with fresh
|
@sujitykulkarni, no that is not due to the broken publish, that sounds like a network issue or a problem on the npmjs servers. The publish issue is an issue in the way the production build servers prepare the tarball, and turns out that even though we have a pre-package step the publish was re-creating it without have full access to all of the packages (on the publish servers) the fix for this is in PR #1557 |
PR is merged, back on the waiting for official internal build generation before publishing -- hopefully this will complete within the next few hours (yes can take this long 😢 ) |
Ok, finally published!!! If there are still issues related to this please comment here and I'll jump on it. |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Description/Screenshot
Steps to Reproduce
Expected behavior
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: