Forced allowSyntheticDefaultImports in tsconfig
See original GitHub issueI just added this to my project. Very neat. However, is it necessary to force client tsconfig
s to enable allowSyntheticDefaultImports
? Looking at the react-circular-progressbar
types there are only two imports to React
using synthetic default imports.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:2
- Comments:10 (9 by maintainers)
Top Results From Across the Web
TSConfig Option: allowSyntheticDefaultImports - TypeScript
This option brings the behavior of TypeScript in-line with Babel, where extra code is emitted to make using a default export of a...
Read more >Understanding esModuleInterop in tsconfig file - Stack Overflow
So allowSyntheticDefaultImports will not report an error if we want to import default from a third-party module which doesn't have a default ...
Read more >Troubleshooting Handbook: tsconfig.json
You can find all the Compiler options in the TypeScript docs. The new TS docs also has per-flag annotations of what each does....
Read more >jsconfig.json Reference - Visual Studio Code
Tip: jsconfig.json is a descendant of tsconfig.json, ... allowSyntheticDefaultImports, Allow default imports from modules with no default export.
Read more >How to optimize a serverless typescript eslint webpack setup ...
Optimising Typescript — tsconfig.json. Include **/*.ts files only and Exclude node_modules and build directories. Remove comments from the bundle ...
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
@ethanae merged your PR and released it in v2.0.2. I’ve tested it out and it appears to work - please let me know if you still encounter any issues. Thank you for raising the issue and submitting a fix!
@Rodrico I haven’t heard back in a while so I’m going to close this issue. But if the issue you had persists in v2.0.3, please let me know!