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
ES module replacement changed in Node 18.6 #495
Comments
Can you share what version of quibble you're using? @giltayar just made a change in quibble@0.6.12 that likely fixes this |
Looks like I'm on 0.6.8 right now. I'll check that updating fixes it. |
The update fixes exactly that. :-) |
Verified that updating quibble to 0.6.12 in my environment fixes the issue; thanks! |
Found this issue on google, so hope this helps anyone who also does... Had the same issue with Mocha 10 combined with ts-node 10.7.0. Updated ts-node to 10.9.1 and that fixed the issue. Of note... I'm on Node LTS 16.17.0, which means the change has been backported. I'm not sure what the best solution for loading typescript into mocha is in 2022, but if using experimental features is still necessary, I'd rather just with naked Node.js or Vitest instead. |
Description
Node 18.6 breaks ES module replacement.
Issue
Starting from Node 18.6.0, the ES module replacement API provided by node is changed in an incompatible way that causes runtime failure. Representative output from running my package's tests:
Environment
node:current
docker image, currently corresponding to 18.6.0 (node@sha256:c9504e6bdd0498b99acbf392b94e4d0d56b2c6a37e52b5766cfb909894d9f389
).The text was updated successfully, but these errors were encountered: