Skip to content
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

Re-evaluate fast functionality #289

Open
nycdotnet opened this issue Oct 8, 2015 · 2 comments
Open

Re-evaluate fast functionality #289

nycdotnet opened this issue Oct 8, 2015 · 2 comments

Comments

@nycdotnet
Copy link
Contributor

The current fast and watch functionality may possibly be improved by considering integration with --isolatedModules and the native watch functionality. Perhaps not. Any thoughts are welcome.

//cc: @basarat

Known bug: .tscache files are still written to disk even in the presence of a testExecute value.
Issue: Very noisy (#191)
Watch functionality does not provide errors if given invalid values (such as a glob).

@jbrantly
Copy link
Member

jbrantly commented Oct 8, 2015

As I understand it grunt-ts actually executes tsc directly. I could be mistaken but I'm not sure that --isolatedModules actually provides any speed increase unless you're using the transpileModule TS API. I'm purely basing this off the comments here and here. Namely:

the idea is you would use this with in a normal compilation, with multiple files, to ensure you can do the compile them in isolation later, hence the "s".

@basarat
Copy link
Member

basarat commented Oct 8, 2015

Yeah, isolatedModules is mostly for error reporting about someone using things that not safe for transpilation. For fast we only give TypeScript one file ... so will not have any impact

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants