We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
@internal
In short:
--production
As discussed previously on discord (link to original message, link to subsequent thread), the above requirements can be met by the @internal tag. However, given that:
I would much prefer to mark the whole directory as being "internal" rather than tagging each export individually in the code.
Similar to how the knip config file allows me to ignore files, I would like to mark files/directories as internal via the config file. E.g.
// knip.ts const knipConfig = { ignore: [ 'src/someExceptionalFile.ts', ], internal: [ 'src/testHelpers/', ], }; export default knipConfig;
This would be equivalent to adding the @internal tag to everything that's exported from that module or directory.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Context
In short:
--production
mode:As discussed previously on discord (link to original message, link to subsequent thread), the above requirements can be met by the
@internal
tag. However, given that:I would much prefer to mark the whole directory as being "internal" rather than tagging each export individually in the code.
Proposal
Similar to how the knip config file allows me to ignore files, I would like to mark files/directories as internal via the config file. E.g.
This would be equivalent to adding the
@internal
tag to everything that's exported from that module or directory.The text was updated successfully, but these errors were encountered: