You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently import specifier resolution matches node's ES module resolution and does not support
automatic resolution of file extensions and the ability to import directories that have an index file.
Node will implement a flag (for now experimental) that will allow customizing the esm specifier resolution algorithm.
To match that a specifierResolution option could be added with a default explicit value
When the option is set to implicit the plugin could automatically resolve file extensions and directories similar to https://nodejs.org/dist/latest-v15.x/docs/api/esm.html#esm_customizing_esm_specifier_resolution_algorithm.
Hey folks. This issue hasn't received any traction for 60 days, so we're going to close this for housekeeping. If this is still an ongoing issue, please do consider contributing a Pull Request to resolve it. Further discussion is always welcome even with the issue closed. If anything actionable is posted in the comments, we'll consider reopening it. ⓘ
Feature
Currently import specifier resolution matches node's ES module resolution and does not support
automatic resolution of file extensions and the ability to import directories that have an index file.
Node will implement a flag (for now experimental) that will allow customizing the esm specifier resolution algorithm.
To match that a
specifierResolution
option could be added with a defaultexplicit
valueWhen the option is set to
implicit
the plugin could automatically resolve file extensions and directories similar to https://nodejs.org/dist/latest-v15.x/docs/api/esm.html#esm_customizing_esm_specifier_resolution_algorithm.Somewhat related to #693
The text was updated successfully, but these errors were encountered: