This project is read-only.

Please fix critical bugs blocking large-scale development - TFS integration and the WScript 8192 issue

Topics: General
Jan 30, 2013 at 1:49 PM

We are actively building large-scale TypeScript projects, and are crippled by two critical bugs that are hampering our development efforts.

Firstly, if a .js output file is marked as read-only on disk, the compiler fails the build.  This is particulary painful when using TFS, as the output .js files MUST be part of a project in order to use Deployment Scripts through MSDeploy.  Our build server often fails on this step, and it is nigh impossible to track down exactly which file is causing the issue.

This issue has been reported here.

Secondly, a large-enough TypeScript project will fail a build if the combined number of characters in the command line exceed 8192 characters.  This issue is critical.  Any project with more than 30 to 40 files will quickly break this barrier.  We have been forced to break up our projects into many smaller ones to get around this issue.   This problem causes issue #1.

This second issue has been reported here:

While I thoroughly agree that TypeScript is an excellent tool to tackle large-scale javascript development - without these two issues being fixed, we cannot create large multi-file projects, or use TFS ??






Jan 30, 2013 at 4:38 PM

Thanks for the feedback.  Looking at those two bugs:

The first (#371) is slated to be fixed for the next release.  I've gone ahead and updated the bug to reflect that. 

The second (#597) appears to already be fixed in the 'develop' branch.  I see one changeset that addresses the issue (, so the fix is in place but may not have been fully tested, yet.  If you can, please let us know if this fixes the issue you were seeing.


Jan 31, 2013 at 2:24 PM
Hey jonturner,
Many thanks for your reply.
Am seriously looking forward to the next release - I just spent the past day and a half splitting 3 TypeScript Projects into 12 separate projects to get around the WScript 8192 issue.
Will have a look at the develop branch over the weekend to fix the .js issue.