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

tscommand.tmp.txt #8

Open
bestander opened this issue Oct 11, 2013 · 11 comments
Open

tscommand.tmp.txt #8

bestander opened this issue Oct 11, 2013 · 11 comments

Comments

@bestander
Copy link

Hi, is this file necessary to be created in root folder?

@basarat
Copy link
Member

basarat commented Oct 11, 2013

Unfortunately yes. You can add it to your git ignore, if that is what concerns you.

The reason we have this file is that when you have a large number of files passing all the file names as a command line option to tsc seems to have issues (it gets stuck). However using a file containing the options along with @file command line option to tsc works fine.

@mindplay-dk
Copy link

I'm fine with creating a temporary file during compilation, but is there any reason you can't clean it up after running it?

The file is regenerated on subsequent runs anyway, correct? It's not used as a "cache" file by any means?

@basarat
Copy link
Member

basarat commented Nov 11, 2013

The plan is to delete it if verbose is off : #15

@cloakedninjas
Copy link

I'm still getting these no matter if run with --verbose or not.

Could these files be created in the .tscache directory instead? Thus keeping all grunt-ts related files in a single place and requiring only a single .gitignore entry.

@thamacher
Copy link

Same with me, when I declare verbose:false in the tsconfig.json. Verbose does not seems to make a difference. Any progress here?

@cleavera
Copy link

cleavera commented Jun 29, 2016

Can we look at reopening this issue? Just because they need to be created doesn't mean it should just sit in the root creating more and more of these files every time it runs

@nycdotnet nycdotnet reopened this Jun 30, 2016
@nycdotnet
Copy link
Contributor

PRs accepted. Sorry I didn't realize this was actually a problem. It may not manifest on Windows because I've never noticed the files staying.

@hamtho
Copy link

hamtho commented Jun 30, 2016

I experienced the same thing on linux. So there it is still an issue.

@mailmrmanoj
Copy link

Why is this file being created?

@nycdotnet
Copy link
Contributor

It's a workaround for an old bug. PRs accepted to delete it.

@tzachshabtay
Copy link

This is happening to me on Windows too, so it's not just a Linux issue.

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

10 participants