exporting a type outside of its declaration incorrectly outputs an export
See original GitHub issueUsing sucrase 3.9.3, this valid TypeScript
interface Test {
}
type Test2 = number;
export { Test, Test2 };
export default Test;
outputs js that exports objects Test
and Test2
, which don’t exist.
Issue Analytics
- State:
- Created 5 years ago
- Comments:11 (6 by maintainers)
Top Results From Across the Web
Export a type after its declaration on Typescript 3.8+
I managed to solve my problem: When the --isolatedModuls flag is on, VS Code's TypeScript language service can't tell if the type we're ......
Read more >Export data to a text file - Microsoft Support
This topic explains how to export text files by using the Export Wizard in Microsoft Access. What do you want to do? Understand...
Read more >Documentation - Modules - TypeScript
Exporting a declaration. Any declaration (such as a variable, function, class, type alias, or interface) can be exported by adding the export keyword....
Read more >rollup.js
Rollup allows you to write your code using the new module system, and will then compile it back down to ... Export a...
Read more >Common Export Documents - International Trade Administration
When it comes to selling and shipping your products outside of the United ... price, weight, kind and other specifications) and is a...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I just released a fix for this in 3.10.0.
I’ve got a local branch that fixes this. Tests pass except for extra line break, which I’ll figure out. Hopefully it’s not too terrible. Will make a PR later today or in the morning.