fix(generators): use export type
vs export
#3246
Merged
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.
Summary
Change
export { NextFunction }
toexport type { NextFunction }
and change authentication generator to look for either version when inserting new code.Tell us about the problem your pull request is solving.
I get the following error in
src/declarations.ts
on the line withexport { NextFunction }
:Re-exporting a type when 'isolatedModules' is enabled requires using 'export type'.ts(1205)
.If that suggestion is followed, then running
feathers generate authentication
fails since it is looking for the lineexport { NextFunction }
to insert new code after/before.Are there any open issues that are related to this?
Not that I can find
Is this PR dependent on PRs in other repos?
No