Ignore same-name definitions

[nycdotnet]

It would be nice to have an option to ignore same-name definitions. For example, consider the following default gruntfile.js with the declaration option enabled:

module.exports = function(grunt) {
  grunt.initConfig({
    ts: {
      default : {
        src: ["**/*.ts", "!node_modules/**/*.ts"],
        options: {
            declaration: true
        }
      }
    }
  });
  grunt.loadNpmTasks("grunt-ts");
  grunt.registerTask("default", ["ts"]);
};

Assuming there is a file called foo.ts, this will work fine the first time it is called and compile foo.ts to foo,js, foo.js.map, and foo.d.ts. However, the second time it runs, the glob will capture both foo.ts and foo.d.ts and the result is likely to be error TS2300: Duplicate identifier errors.

Suggested enhancement: if options: declaration is turned on, the default behavior should be to ignore foo.d.ts if foo.ts is being compiled. There should be an option to not ignore the same-name definition files.

when out or files is being used (basically if --out is being passed to tsc), the output js file minus the js extension plus the d.ts extension should be auto-ignored.

[johnman]

I usually get around this by having the output go to a dist directory so the d.ts files that get generated are not taken into account in either builds or watchers (grunt otherwise you could get in a loop where you watch triggers grunt-ts every time grunt ts re-generates the foo.d.ts files unless you start excluding there too).