Skip to content
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

Collector issue for known issues w/ jiti #565

Open
webpro opened this issue Mar 21, 2024 · 0 comments
Open

Collector issue for known issues w/ jiti #565

webpro opened this issue Mar 21, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@webpro
Copy link
Owner

webpro commented Mar 21, 2024

There's a number of issues around using jiti. First and foremost: Jiti is awesome, Knip wouldn't nearly be as good without it!

This is a collector issue for housekeeping, and I expect those to be resolved at once. issues are documented at https://knip.dev/reference/known-issues

I think most or all of them can be potentially worked around by using bun:

bunx --bun knip

This uses the Bun runtime. Bun does not transpile, just strips types, has flexible module resolution, and also uses TS path aliases (tsconfig.json#compilerOptions.paths) in dynamically loaded scripts/modules.

jiti v2 might fix the issues for the Node.js runtime.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant