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
Currently, CRA suggests allowJs in tsconfig to be true. But, together with isolatedModules, this causes problems whenever there are .js files in the codebase. Specifically it causes microsoft/TypeScript#15230: "Cannot compile namespaces when the '--isolatedModules' flag is provided."
.js files can be introduced naturally a number of ways, e.g. by following instructions to add setupTests.js, setupProxy.js, etc., or by tools that generate .js files (e.g. protobuf, pegjs, etc.).
I think this is not needed because TS is only used for typechecking and not transpilation. Babel and webpack together already make sure to include any imported/required .js files in the output bundle.
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had any recent activity. It will be closed in 5 days if no further activity occurs.
This issue has been automatically marked as stale because it has not had any recent activity. It will be closed in 5 days if no further activity occurs.
Currently, CRA suggests allowJs in tsconfig to be true. But, together with isolatedModules, this causes problems whenever there are .js files in the codebase. Specifically it causes microsoft/TypeScript#15230: "
Cannot compile namespaces when the '--isolatedModules' flag is provided.
".js files can be introduced naturally a number of ways, e.g. by following instructions to add setupTests.js, setupProxy.js, etc., or by tools that generate .js files (e.g. protobuf, pegjs, etc.).
I think this is not needed because TS is only used for typechecking and not transpilation. Babel and webpack together already make sure to include any imported/required .js files in the output bundle.
The text was updated successfully, but these errors were encountered: