Conversation
commit: |
|
Thank you!
There is no way to express this. Also see #1442 for an outstanding issue/idea. |
|
🚀 This pull request is included in v5.88.0. See Release 5.88.0 for release notes. Using Knip in a commercial project? Please consider becoming a sponsor. |
yeah this is a good idea. I think most entry points need default exports, but customized named exports sounds good too. |
|
🚀 This pull request is included in v6.0.0-2. See Release 6.0.0-2 for release notes. Using Knip in a commercial project? Please consider becoming a sponsor. |
Hi 👋
I recently wrote a raycast plugin, but knip doesn’t know about its file structure yet, so I added a plugin:
Raycast uses the
commandssection inpackage.jsonto find commands:src/name-of-the-command{.ts,.tsx,.js,.jsx}src/tools/name-of-the-tool{.ts,.tsx,.js,.jsx}Question: Only the
defaultexport of commands and tools should be seen as used by knip - I haven’t found a way to express this though. Is this something that knip supports? I think right now the whole file becomes an entry point ...Note: This PR was done with AI assistance.