You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
List of keywords you searched for before creating this issue. Write them down here so that others can find this suggestion more easily and help provide feedback.
β Viability Checklist
My suggestion meets these guidelines:
This wouldn't be a breaking change in existing TypeScript/JavaScript code
This wouldn't change the runtime behavior of existing JavaScript code
This could be implemented without emitting different JS based on the types of the expressions
This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
Note: They are different when transforming to JavaScript.
The first statement will be removed and the second will be export {} from "mod" or import "mod".
When it comes to re-export, for example,
export*from"mod";
If we try to write
exporttype*from"mod";
We will get a TS1383 error.
Only named exports may use 'export type'.
π Motivating Example
To be added.
I have no strong need for it, just as a record.
π» Use Cases
export * from "mod" will generate runtime export statement. To avoid this, one has to list all the type.
exporttype{foo,bar,baz, ...andmore}from"mod";
The text was updated successfully, but these errors were encountered:
Suggestion
π Search Terms
List of keywords you searched for before creating this issue. Write them down here so that others can find this suggestion more easily and help provide feedback.
β Viability Checklist
My suggestion meets these guidelines:
β Suggestion
Allow re-export type.
We can use
export from
statement in JavaScript..and in TypeScript, we can export type from another module.
Note: They are different when transforming to JavaScript.
The first statement will be removed and the second will be
export {} from "mod"
orimport "mod"
.When it comes to re-export, for example,
If we try to write
We will get a TS1383 error.
π Motivating Example
To be added.
I have no strong need for it, just as a record.
π» Use Cases
export * from "mod"
will generate runtime export statement. To avoid this, one has to list all the type.The text was updated successfully, but these errors were encountered: