named exports are not resolved relatively
See original GitHub issuei defined a few named exports
"namedExports" : {
"af/util/make" : [ "Make", "hasPrototype", "Mixin"],
"af/modules/DataBinding/Parser" : ["ObjectParser", "parseExpression", "assignExpression"]
}
but when I import those functions the paths are not resolved.
Lookup path is src, my module is in src/af/modules/DataBinding/StyleBinding.js and I’m importing e.g. Make. The path added by ImportJS is af/util/make and not ../../util/make.
Issue Analytics
- State:
- Created 7 years ago
- Comments:6
Top Results From Across the Web
ESM named exports are not available with "type": "module"
I believe the issue is that while NodeJS treats your index.js as an ES module, it doesn't resolve the graphql import to its...
Read more >How to fix/disable seemingly erroneous "No named exports ...
I believe the report is a false positive because when I run the code, everything works fine and I can indeed import the...
Read more >Modules • JavaScript for impatient programmers (ES2022 ...
A module can have both named exports and a default export, but it's usually better to stick to one export style per module....
Read more >Change: Prefer default export to no default export (#20) · Issues
It's possible to sum this up in a fairly simple rule: "Vue single file components have a default export, everything else has named...
Read more >JavaScript default exports aren't always fun, or how I ...
Named exports are just what they sound like – you export them by name, and can have any ... Objects are not valid...
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 Free
Top 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

It works great now 👍
Sorry, I forgot about that - thanks for the reminder! I just published
atom-import-js@v0.2.2which includes these changes.