-
-
Notifications
You must be signed in to change notification settings - Fork 185
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
Wrong module returned when both dir and file has same name #211
Comments
Actually, copying my fix from the Jest PR makes the tests I added here pass (it also fixes the test in the reproduction repository) - I'll open up a PR |
ljharb
pushed a commit
to SimenB/resolve
that referenced
this issue
Feb 5, 2020
ljharb
pushed a commit
that referenced
this issue
Feb 5, 2020
ljharb
pushed a commit
that referenced
this issue
Feb 5, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Pretty much the same as #51, but from within the directory this time. See https://github.com/SimenB/resolve-file-and-dir-name-clash-bug
It works correctly for
./
but not.
.Swapping
resolve/lib/sync.js
Line 78 in f4b27af
to
"fixes" the issue, but breaks the test added for #51.
Here are two failing unit tests (for
sync
andasync
):This was originally reported to Jest in jestjs/jest#8910 (Jest uses a forked implementation of
resolve
under the hood). You can look at my PR which fixes it in Jest. It stalled since I wasn't happy with the implementation, but maybe you can draw inspiration from it, I dunno 🙂 jestjs/jest#8912The text was updated successfully, but these errors were encountered: