-
Notifications
You must be signed in to change notification settings - Fork 30.2k
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
test_runner: using module mocking confuses all future esm imports to use cjs path resolution #53807
Labels
loaders
Issues and PRs related to ES module loaders
test_runner
Issues and PRs related to the test runner subsystem.
Comments
ChALkeR
changed the title
test_runner: using module mocking confuses all future esm imports to load
test_runner: using module mocking confuses all future esm imports to use cjs path resolution
Jul 11, 2024
.js
suffix by default
Also Hi! Kind reminder you're welcome to come back :P! |
avivkeller
added
test_runner
Issues and PRs related to the test runner subsystem.
loaders
Issues and PRs related to ES module loaders
labels
Jul 11, 2024
I'd like to solve this in two days. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
loaders
Issues and PRs related to ES module loaders
test_runner
Issues and PRs related to the test runner subsystem.
Version
v22.4.1
Platform
Subsystem
test_runner
What steps will reproduce the bug?
Or, alternatively:
Or, alternatively (dir imports):
How often does it reproduce? Is there a required condition?
Always, when run with
--experimental-test-module-mocks
What is the expected behavior? Why is that the expected behavior?
What do you see instead?
Additional information
Likely from #52848, cc @cjihrig, @nodejs/test_runner
Also: long time no see, hi all!
The text was updated successfully, but these errors were encountered: