Typescript: Empty output file when compiling

Question

I compile the following code using the latest typescript compiler (1.4)

/// <reference path="typescript.d.ts" />

//import ts = require("typescript");
module cc {
console.log("Hello");
}

using the following compile args

node /TypeScript/built/local/tsc.js -m commonjs --noEmitOnError app.ts -out myApp.js

which compiles Ok and generates the "myApp.js" file.

When I uncomment the import line, I get no error on compiling, but it generates an empty (zero size) "myApp.js" and a file "app.js", even I have specified the --noEmitOnError switch.

This is a strip down example, in fact I specify multiple ".ts" files and I get no error on compiling, the empty "myApp.js" file and for each ".ts" file I specified, I get a ".js" file.

I am using node 0.10.30 on Windows 8.1

It's a local copy of /TypeScript/built/local/typescript.d.ts — Panos Theof
– Panos Theof, Commented Dec 18, 2014 at 14:44
I see this behavior as well. What happens if you rename the typescript.d.ts file to somethingelse.d.ts and try to import that instead? If it "works" by saying that it's not an external module, then you may have uncovered a bug that should be reported on GitHub. — NYCdotNet
– NYCdotNet, Commented Dec 18, 2014 at 15:33

Ryan Cavanaugh · Accepted Answer · 2014-12-18 16:34:40Z

5

The --out flag generally should not be used with external modules. Only code that is not part of an external module will be written to the specified output file. Files with a top-level import are an external module.

See also modules documentation, this GitHub issue tracking

answered Dec 18, 2014 at 16:34

Ryan Cavanaugh

223k59 gold badges280 silver badges235 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Typescript: Empty output file when compiling

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related