chore: witch to explicit type exports and enable verbatimModuleSyntax.
#24
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
typeexports, following TypeScript best practices and ensuring a type is never used as a value.verbatimModuleSyntaxfor better adherence to TypeScript module syntax standards. It will also cause a build error if a type is used as value (class, constant, ...).Background
I encounter errors when enabling verbatimModuleSyntax on my NestJS app, with errors reported from
nestjs-dataloader: TS will complain that types are exported as values: