How to stop Typescript compiler from generating JS and JS.MAP files in Visual Studio 2017?

Question

I have a few typescript files for my app myapp in my Visual Studio 2017 ASP.NET project. I use a gulp task to generate the JS files, so I don't want the build or language service creating these JS and JS.MAP files.

This is how my TSCONFIG file look like:

{
  "compileOnSave": false,
  "compilerOptions": {
    "noImplicitAny": false,
    "noEmitOnError": true,
    "removeComments": false,
    "sourceMap": true,
    "moduleResolution": "node",
    "emitDecoratorMetadata": true,
    "experimentalDecorators": true,
    "target": "es5",
    "module": "system",
    "types": [ "" ],
    "lib": [
      "es6",
      "dom"
    ]
  },
  "include": [
    "./myapp/**/*"
  ]
}

I tried the following:

I added the myapp to the exclude section of the tsconfig.js. Both the js and js.map are not generated at that time if I close Visual Studio and open again. But I see a lot of compilation errors.
I added <TypeScriptCompileBlocked>true</TypeScriptCompileBlocked> to the .csproj file. I closed VS 2017, opened again and did a build. I see the JS and JS.MAP files.
I changed the BuildAction property to none, but still see the JS and JS.MAP files

What should I do so the syntax check of the TS file will work but does not generate any JS and JS.MAP files?

Possible duplicate of How to prevent visual studio 2017 from build javascript? — Arg0n
– Arg0n, Commented Aug 28, 2017 at 13:39
The issue I have is different. I don't do a build option from the menu from Visual Studion. I just close and open the project and start seeing these behaviors. — wonderful world
– wonderful world, Commented Aug 28, 2017 at 15:08
I know this is a bit old, but if your problem is mainly the js.map, you can just set sourceMap to false on tsconfig — dege
– dege, Commented Dec 3, 2018 at 17:38
@wonderfulworld your VS is actually running TSC command each time to check for TS errors (it reads tsconfig.json) which without "noEmit": true will output JS files to your folder... — dkocich
– dkocich, Commented Sep 2, 2020 at 11:26

Nathaniel · Accepted Answer · 2020-06-04 14:36:46Z

16

Try add "noEmit": true in your tsconfig. It should prevent the .js .js.map from generating.

answered Jun 4, 2020 at 14:36

Nathaniel

6577 silver badges11 bronze badges

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

3 Comments

Christopher Thomas Over a year ago

This doesn't work for me, do you know of any reason why this would be the case?

Nathaniel Over a year ago

@ChristopherThomas Check your typescript version, if it's older than 4.0 then there's a flag called "incremental": true that confict with "noEmit": true

quilkin Over a year ago

also works in VS Code

Rohan Prasad · Accepted Answer · 2020-12-23 09:47:37Z

5

Try add "noEmitOnError": true in your tsconfig. It should prevent the .js .js.map from generating if there is any error in the TS files(s).

answered Dec 23, 2020 at 9:47

Rohan Prasad

1612 silver badges3 bronze badges

Comments

Miikee · Accepted Answer · 2021-05-19 15:07:46Z

3

If Visual Studio seems to be ignoring the noemit option in the tsconfig file, edit your project file. In the project file, go to the <PropertyGroup> that contains the rest of the TypeScript options and add <TypeScriptNoEmit>True</TypeScriptNoEmit> between that PropertyGroup's open and closing tags.

answered May 19, 2021 at 15:07

Miikee

811 silver badge4 bronze badges

2 Comments

Dezzamondo Over a year ago

This one did it for me. NOTE: You may need to restart VS after changing the project file for the changes to take effect.

Volodymyr Kotylo Over a year ago

works in VS2022 without restart (just reload project), thanks

Rob · Accepted Answer · 2021-06-30 04:22:15Z

1

I noticed that if I created the file using angular it didn't emit a .js but if I added a new TypeScript file from Visual Studio via the New Item menu it did. Turns out the latter sets the Build Action to "TypeScript file" whereas the former sets the build action to None, Do Not Copy. I changed the offending TypeScript files to None and it's stopped the .js files being generated. This is contrary to the OPs statement that it had no affect - but in my case it worked. Setting noEmit: true just resulted in no vendor.js file being generated for my angular ng build.

edited Jun 30, 2021 at 4:22

answered Jun 30, 2021 at 4:03

Rob

10.3k5 gold badges64 silver badges93 bronze badges

Comments

Swirle13 · Accepted Answer · 2023-11-17 17:33:48Z

0

My issue was I had accidentally deleted "outDir" from my tsconfig.json.

To fix, I added the line back in:

{
  "compilerOptions": {
    ...
    "outDir": "./dist",
    ...
  }
}

From the Typescript Docs - Out Dir:

If specified, .js (as well as .d.ts, .js.map, etc.) files will be emitted into this directory. The directory structure of the original source files is preserved; see rootDir if the computed root is not what you intended.

If not specified, .js files will be emitted in the same directory as the .ts files they were generated from

answered Nov 17, 2023 at 17:33

Swirle13

1249 bronze badges

Collectives™ on Stack Overflow

How to stop Typescript compiler from generating JS and JS.MAP files in Visual Studio 2017?

5 Answers 5

3 Comments

Comments

2 Comments

Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

5 Answers 5

3 Comments

Comments

2 Comments

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related