-
Notifications
You must be signed in to change notification settings - Fork 203
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
Disable emit-on-save in tsconfig.json? #175
Comments
@Deathspike we recommend you use something like : https://github.com/TypeStrong/atom-typescript/blob/master/docs/packages.md#manage-your-projects for now. Having said that I now realize that perhaps it does belong in |
What is the name of this setting? I saw "compileOnSave" in the another thread, this however does not work:
I use webpack so extra js files doesn't make sense. I still want to compile or statically check though, just without extra files. |
Oh I see this link https://github.com/TypeStrong/atom-typescript/blob/master/docs/packages.md#manage-your-projects doesn't contain new information. It's enough to just put in tsconfig a "complieOnSave : false". |
@Ciantic Can I have the link to that thread 🌹 |
I would like to request a feature to disable emit-on-save based on the
tsconfig.json
file. In my situation, I have 2~3 projects living together in the same folder structure. These are the client and server components, sharing some of the definitions and logic with one another using a shared component. I will elaborate on the feature request.The client component is compiled using
browserify
andtsify
. This enables writingnodejs
-like applications which bundles all the dependencies nicely together into a single output file to load into browsers. It also supports source maps, which would otherwise be lost when the files were build into an intermediary file prior to bundling them up withbrowserify
. This component should have emit-on-save disabled.The other component is a NodeJS-based application. It serves as the server back-end for the client component. Bundling this up would be awkward and silly, so the emit-on-save facilities save time and provide nice integration with the editing experience. Furthermore,
node-inspector
debugging is quite happy with the emits I can make from the editor like this. No further build or watchers necessary, so this is great here.Would it be a reasonable idea to enable/disable emit-on-save per project, rather than on/off?
The text was updated successfully, but these errors were encountered: