-
Notifications
You must be signed in to change notification settings - Fork 12.8k
Very slow compilation with allowJs #10157
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
On a similar note, would it be possible to have a different config for JS files? That way you could not only change "moduleResolution" but also properties like "allowUnreachableCode". Ideally for JS that is being migrated I don't want any compiler linting. I have tried using two instances of TS webpack loaders to handle JS and TS separately, but with no luck. |
I am using TypeScript with webpack and I can't even get the app to run locally with |
@abobwhite do you see the same behavior running outside of webpack (i.e. |
Also one common issue we see is excluded files. with |
Thanks @mhegazy Your comments helped point me in a slightly different direction. It turns out it was a ts-loader setting I needed. I needed to set |
Automatically closing this issue for housekeeping purposes. The issue labels indicate that it is unactionable at the moment or has already been addressed. |
TypeScript Version: 2.1.0-dev.20160803
Trying to migrate medium size
js
project tots
so I am usingallowJs: true
in tsconfig.json and have mix ofts
(10%) andjs
(90%) files alreadyUnfortunately compilation time with
allowJs:true
is 23 seconds while withallowJs:false
is 3 seconds.Problem seems to be that all js files follow the
node_modules
("moduleResolution": "node"
in tsconfig.json)Is there any way to have
moduleResolution:classic
forJS
part whilenode
forTS
or some other way to configure the project so thatjs
files are not so deeply analyzed.Here are the stats:
with
allowJs:true
with
allowJs:false
The text was updated successfully, but these errors were encountered: