This fixes a small oversight: ExportSpecifier supports exportKind in a similar fashion to ImportSpecifier supporting importKind, but the print logic was missing.
Without this change it's impossible to generate an ExportNamedDeclaration containing a mix of type and value exports.
This fixes a small oversight:
ExportSpecifier
supportsexportKind
in a similar fashion toImportSpecifier
supportingimportKind
, but the print logic was missing.Without this change it's impossible to generate an ExportNamedDeclaration containing a mix of type and value exports.
See this broken jscodeshift example in AST Explorer
This is in the spirit of changes described in the original type-only PR for TypeScript, as well as changes for SWC in 1.2.92