-
Notifications
You must be signed in to change notification settings - Fork 12.8k
--isolatedModules
should warn about re-export of type
#15231
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hm... what exactly is I have been using it as a way of requiring that only files parsed as "module" would be considered valid (i.e. requires at least one "import" or "export" in typescript, forbids (potentially sloppy) scripts), though preventing reexporting of types would break things on my project. I can turn of |
It guarantees that the file can be transpiled in isolation. Hence the isolated part. Things that need cross file information to emit like namespaces spanning multiple files or const enums are not alloewd. This is what you would use if you were using transpileModule API. |
So I assume the absence of If that is the case, disabling |
|
@Andy-MS ah, that happens sometimes in github. The thing in question was about |
TypeScript Version: nightly (Version 2.3.0-dev.20170417)
Code
a.ts
b.ts
Expected behavior:
An error saying that the emit of
b.ts
depends on the contents ofa.ts
.Actual behavior:
b.js
isexport { A } from "./a";
.The text was updated successfully, but these errors were encountered: