Support for platform specific extension breaks "directories as modules"
See original GitHub issueConsider the following file hierarchy
Prior to version 1.3.0, @import "uikit/style/common"
was correctly resolved, consistent with the node.js resolution: uikit-lib
was considered like a module named uikit
because of its package.json.
In version 1.3.0, import paths do not include the correct “node.js” resolution of uikit
.
(Including package.json
in directories other than real modules is useful to avoid relative paths and for Git submodules)
Thanks!
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
File extension/directory index resolution in ESM #268 - GitHub
Arguments against supporting file extension/directory index resolution automatically. Browsers don't automatically resolve file extensions or ...
Read more >Moving modules breaks system [#2651144] | Drupal.org
According to the documentation, all one has to do if one wants to move modules into a custom or contrib directory structure is...
Read more >'Directory import is not supported resolving ES modules' with ...
With ES6 modules you can not (yet?) import directories. Your import should look like this: import database from "./database/index.js".
Read more >modulefile — Modules documentation
The Modules Package uses commands which are extensions to the "standard" Tool Command Language Tcl(n) package. Unless otherwise specified, the Module commands ...
Read more >Migrating From JDK 8 to Later JDK Releases
Code that uses only official Java SE Platform APIs and supported JDK-specific APIs should continue to work without change. Code that uses JDK-internal...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@pierre-elie I managed to to reproduce the issue and fix it. Please test v1.3.1 and let me know if the issue is now fixed. 😃
Great! Please let me know if you find something else that is not working 😃