-
-
Notifications
You must be signed in to change notification settings - Fork 22
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
Running object.assign under SES #82
Comments
hmm - how could the object be frozen? it's a function created inside that file (not the one that gets shimmed to |
Enzyme seems to be using
is object frozen true [Function: assign] Function <Function <[Object: null prototype] {}>>
is object frozen true [Function: assign] Function <Function <[Object: null prototype] {}>>
is object frozen true [Function: assign] Function <Function <[Object: null prototype] {}>>
is object frozen true [Function: assign] Function <Function <[Object: null prototype] {}>>
is object frozen true [Function: assign] Function <Function <[Object: null prototype] {}>>
is object frozen true [Function: assign] Function <Function <[Object: null prototype] {}>> |
Ah, that bug was fixed in fc41c80, which is available in v4.1.1 and higher :-) feel free to update! |
Great! Thank you! |
Hi @ljharb, I'm trying to use Enzyme under
SES
, and I'm running into an issue that involves theobject.assign
package anddefine-properties
package, although it may be solved by something lower down in the dependency tree.Here's what I'm seeing:
It seems like the most obvious solution is to change define-property to return early if the object is frozen, but I'm not sure this is the right approach.
Thanks!
The text was updated successfully, but these errors were encountered: