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
import "./package.js" is treated the same as "package" #377
Comments
I'm having the same issue. I have a file If I rename the file to |
Also hitting this (a file called |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I just ran into a rare edge case where
madge
is resolving./package.js
andpackage
(from npm) to be the same. This gave me weird cyclic dependencies when there were actually none.This is in the context of a Typescript codebase strictly using ES6 syntax.
The text was updated successfully, but these errors were encountered: