-
Notifications
You must be signed in to change notification settings - Fork 29.7k
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
Assertion error starting from v14.0.0 #33334
Comments
node/lib/internal/modules/cjs/loader.js Lines 945 to 950 in 94e5b5c
It looks like |
Maybe we could use /cc @addaleax |
4 tasks
BridgeAR
added a commit
to BridgeAR/node
that referenced
this issue
May 11, 2020
In case the exported module is a proxy that has the `getPrototypeOf` or `setPrototypeOf` trap, skip the circular dependencies check. It would otherwise be triggered by the check itself. Fixes: nodejs#33334 Signed-off-by: Ruben Bridgewater <ruben@bridgewater.de>
codebytere
pushed a commit
that referenced
this issue
May 16, 2020
In case the exported module is a proxy that has the `getPrototypeOf` or `setPrototypeOf` trap, skip the circular dependencies check. It would otherwise be triggered by the check itself. Fixes: #33334 Signed-off-by: Ruben Bridgewater <ruben@bridgewater.de> PR-URL: #33338 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Zeyu Yang <himself65@outlook.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Our code:
We want to export a proxified object and explicitly ensure that user code will not trigger certain traps. Works fine in v12.x. Throws assertion error in v14.x, but we did not call
getPrototypeOf
.We bisected to d7452b7. Throws error even with
--no-warnings
.Please Node.js team, can you fix this? Thanks.
The text was updated successfully, but these errors were encountered: