-
Notifications
You must be signed in to change notification settings - Fork 6
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
If the resolved partial is extensionless, then find a file like it #8
Comments
mrjoelkemp
added a commit
to dependents/node-dependency-tree
that referenced
this issue
May 21, 2016
There's no need to skip files that use loaders. In fact, we want those files to be properly resolved since they're part of the dependency tree of a module. We skipped them only because module-lookup-amd couldn't handle those files. Ref dependents/node-module-lookup-amd#8
mrjoelkemp
added a commit
to dependents/node-dependents-editor-backend
that referenced
this issue
May 25, 2016
mrjoelkemp
added a commit
to dependents/node-dependents-editor-backend
that referenced
this issue
May 25, 2016
mrjoelkemp
added a commit
to dependents/node-dependents-editor-backend
that referenced
this issue
May 25, 2016
mrjoelkemp
added a commit
to dependents/node-dependents-editor-backend
that referenced
this issue
May 25, 2016
mrjoelkemp
added a commit
to dependents/node-dependency-tree
that referenced
this issue
Jun 3, 2016
There's no need to skip files that use loaders. In fact, we want those files to be properly resolved since they're part of the dependency tree of a module. We skipped them only because module-lookup-amd couldn't handle those files. Ref dependents/node-module-lookup-amd#8
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When you're importing templates or styles, it's incorrect to assume that they have the same extension as the file importing them.
Consumers shouldn't have to guard against this non-existent result.
The text was updated successfully, but these errors were encountered: