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
fix(node-resolve): Fix bug where JS import was converted to a TS import, resulting in an error when using export maps #921
fix(node-resolve): Fix bug where JS import was converted to a TS import, resulting in an error when using export maps #921
Commits on Jul 1, 2021
-
-
always return
null
fromresolveId
if file not foundso that other candidates in `importSpecifierList` can be tried
Commits on Jul 4, 2021
-
-
-
shuffle
importSpecifierList
order so that the original import has t……op priority and with a later commit will be the only one that export maps are tried on
-
refactor
resolveImportSpecifiers
to separate classic and exports al……gorithm and to try the exports algorithm first, and only with the first id
-
-
-
-
-
-
-
also try all import specifiers with exports algo
but the first one that supports exports, but had an error, will result in an error
-
Revert "also try all import specifiers with exports algo"
This reverts commit 7730f36.