-
Notifications
You must be signed in to change notification settings - Fork 30k
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
defining Object.prototype.then
causes esm loader to throw an error
#45035
Comments
This is not really possible to fix. If you're trying to monkey-patch some code, I'd suggest modifying the specific objects you're working with rather than |
I'm (trying) to run a WPT that modifies Object.prototype and crashes the entire runner. If it's not possible to fix it can be closed :) |
aduh95
added a commit
to aduh95/node
that referenced
this issue
Oct 17, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version
v18.11.0
Platform
Microsoft Windows NT 10.0.19043.0 x64
Subsystem
No response
What steps will reproduce the bug?
How often does it reproduce? Is there a required condition?
N/A
What is the expected behavior?
It would be great not to throw an error.
What do you see instead?
If you import/dynamically import something before setting Object.prototype.then, you get this error:
however if you use a dynamic import after it, you get a different error:
Additional information
this is a very niche use case
The text was updated successfully, but these errors were encountered: