-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
Fix non-extendable objects regression of 1.1.0 #5658
Conversation
Looks like this hack makes Phantom go crazy. Not sure how to fix the tests... |
OK the tests seem to be running OK! Had to upgrade the Node version on Travis after some deps upgrades because of some compatibility bugs. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 nice hack! Given the current situation I think this is good solution.
Closes #5650 until we figure out a less hacky solution.
This is breaking in an environment where Update: Maybe wrapping it in a try-catch would help. Update: PR #6806 created |
Closes #5650 until we figure out a less hacky solution. Tested it locally and it seems to work. I put the redefine in
Util
because it is currently included first in the Rollup build, but this is fragile. The advantage of this solution is that it changes just a few lines of code. cc @calvinmetcalf @perliedman @IvanSanchez