microsoft / microsoft/TypeScript
Provide option to not include `sourceMappingURL` in the generated `.js` file when `sourceMap` is `true`
Nadie ha tomado este issue todavía.
- Lenguaje dominante
- Go
- Estrellas
- 111k
- Forks
- 14.4k
- Merge medio
- 1 d 19 h
- PR fusionados (30 d)
- 117
Descripción
🔍 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:
- set
sourceMaptotrue - run
npx tsc - set
sourceMaptofalse - run
npx tsconce again.
There should provide a compilerOption to disable inclusion of sourceMappingURL in the generated .js file.
💻 Use Cases
-
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.jsfile. -
What shortcomings exist with current approaches?
sourceMappingURLis included in.jsfile. -
What workarounds are you using in the meantime?
- set
sourceMaptotrue - run
npx tsc - set
sourceMaptofalse - run
npx tsconce again.
- set
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Línea de trabajo
El issue no especifica archivos, pruebas ni puntos de entrada del compilador. Empieza siguiendo cómo la opción del compilador sourceMap controla la emisión de archivos .map y el comentario sourceMappingURL. Se considera terminado cuando una opción del compilador documentada puede suprimir ese comentario y seguir emitiendo source maps, con cobertura tanto del comportamiento habilitado como del deshabilitado.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- javascript, typescript
- Área
- compilers
- Tipo de issue
- Nueva funcionalidad
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Estado de actividad
- Estancado
- Claridad
- Bastante claro
- Aptitud para principiantes
- 30/100