We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently we have two ways to define the files include in the compilation process.
exclude
files
It would be much simpler if we could just define some entry files (only modules) and all dependent files will be included in the compilation process automatically. Browserify does something like this (https://github.com/substack/node-browserify#browserifyfiles--opts).
This would drastically simplify the configuration and be very helpful for isomorphic/universal JavaScript apps.
Maybe modules or entryFiles would be a good name for the property in the tsconfig.
modules
entryFiles
tsconfig
The text was updated successfully, but these errors were encountered:
Just put them in "files"; the compiler will follow the imports and include then too. "files" is really "rootFiles".
Sorry, something went wrong.
Thanks, didn't know that!
No branches or pull requests
Currently we have two ways to define the files include in the compilation process.
exclude
property Support "exclude" property in tsconfig.json #3188files
property https://github.com/Microsoft/TypeScript/wiki/tsconfig.jsonIt would be much simpler if we could just define some entry files (only modules) and all dependent files will be included in the compilation process automatically. Browserify does something like this (https://github.com/substack/node-browserify#browserifyfiles--opts).
This would drastically simplify the configuration and be very helpful for isomorphic/universal JavaScript apps.
Maybe
modules
orentryFiles
would be a good name for the property in thetsconfig
.The text was updated successfully, but these errors were encountered: