Provide option to not include `sourceMappingURL` in the generated `.js` file when `sourceMap` is `true`

🔍 Search Terms

• sourceMappingURL
• sourceMap

✅ Viability Checklist

• This wouldn't be a breaking change in existing TypeScript/JavaScript code
• This wouldn't change the runtime behavior of existing JavaScript code
• This could be implemented without emitting different JS based on the types of the expressions
• This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
• This isn't a request to add a new utility type: https://github.com/microsoft/TypeScript/wiki/No-New-Utility-Types
• This feature would agree with the rest of our Design Goals: https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals

⭐ Suggestion

There should be a compilerOption to disable inclusion of sourceMappingURL in the generated .js file when sourceMap is true.

📃 Motivating Example

When sourceMap is true in tsconfig.json, TypeScript compiler generates .map file together with .js file and also include sourceMappingURL in .js file.

The inclusion of sourceMappingURL in .js file is one way of linking generated code with sourcemap.
Another way is to use SourceMap header.

Right now, to make use of SourceMap header without including sourceMappingURL in .js file, I have to:

1. set sourceMap to true
2. run npx tsc
3. set sourceMap to false
4. run npx tsc once again.

There should provide a compilerOption to disable inclusion of sourceMappingURL in the generated .js file.

💻 Use Cases

1. What do you want to use this for?
   I want to use this to use SourceMap header without getting warning in browser. The benefit of using SourceMap header is that the linking of generated file to map file can be controlled by the server without regenerating .js file.

2. What shortcomings exist with current approaches?
   sourceMappingURL is included in .js file.

3. What workarounds are you using in the meantime?

   1. set sourceMap to true
   2. run npx tsc
   3. set sourceMap to false
   4. run npx tsc once again.

In der Issue werden keine Dateien, Tests oder Compiler-Einstiegspunkte genannt. Beginne damit nachzuverfolgen, wie die Compiler-Option sourceMap die Ausgabe von .map-Dateien und den Kommentar sourceMappingURL steuert. Erledigt ist die Aufgabe, wenn eine dokumentierte Compiler-Option diesen Kommentar unterdrücken kann und weiterhin Source Maps ausgegeben werden, mit Abdeckung sowohl des aktivierten als auch des deaktivierten Verhaltens.