We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
*.js
"type": "module"
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
This check can be extended to also allow *.js in ESM contexts:
https://github.com/webpro/knip/blob/cc0fbc69e2aef3570ec0e888b101e57e68239fba/src/util/loader.ts#L28-L32
Why? Hitting a couple of rough edges in Jiti:
No top-level await: unjs/jiti#72 No import.meta.resolve: unjs/jiti#101
import.meta.resolve
Not high priority though, all of this is work-aroundable, just documenting it.
The text was updated successfully, but these errors were encountered:
No "exports" main defined
c082cae
Load .js module using native import call (fixes #290)
aeaf70a
🚀 This issue has been resolved in v2.41.1. See Release 2.41.1 for release notes.
Sorry, something went wrong.
Thanks Alec, good idea, .js modules now use native import().
.js
import()
Thank you!
Knip v5.1 introduces a new workaround: bunx --bun knip
bunx --bun knip
No branches or pull requests
This check can be extended to also allow
*.js
in ESM contexts:https://github.com/webpro/knip/blob/cc0fbc69e2aef3570ec0e888b101e57e68239fba/src/util/loader.ts#L28-L32
Why? Hitting a couple of rough edges in Jiti:
No top-level await: unjs/jiti#72
No
import.meta.resolve
: unjs/jiti#101Not high priority though, all of this is work-aroundable, just documenting it.
The text was updated successfully, but these errors were encountered: