Add `x_google_ignoreList` (Ignore-listing code) support to sourcemaps
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 35/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Bastante claro
- Estado de actividad
- Estancado
- Stack tecnológico
- javascript, rollup
- Área
- build-system
Línea de trabajo
El issue no nombra archivos, tests ni puntos de entrada. Empieza rastreando cómo microbundle delega la generación de sourcemaps a Rollup y, después, compara los mapas generados con la source-map ignoreList specification. La tarea estará terminada cuando los sourcemaps generados identifiquen las fuentes de frameworks o dependencias mediante el campo ignore-list solicitado, con cobertura para las rutas de salida relevantes.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Introduce the x_google_ignoreList extension in the sourcemaps generated by this project. This will facilitate a more streamlined debugging experience in Chrome (and other supporting browsers) by automatically filtering out framework and dependency code.
Benefit
Implementing x_google_ignoreList in the sourcemaps will align this project with modern web development practices, offering a more focused and efficient debugging experience for developers using Chrome DevTools. This change will particularly benefit those who regularly engage in debugging complex applications with numerous dependencies.
Background Context
- https://developer.chrome.com/blog/devtools-modern-web-debugging/#just-my-code
-
The ignore-listing is enabled by populating an extra
x_google_ignoreListfield in the source map that Angular generates when compiling the project. The Chrome DevTools team encourages other framework authors to implement a similar change. Refer to the Case Study: Better Angular Debugging with DevTools post for more details.
-
- https://developer.chrome.com/blog/devtools-better-angular-debugging/#ignore-listing-code
-
Ignore-listing code
When debugging applications using Chrome DevTools, authors generally only want to see just their code, not that of the framework underneath or some dependency tucked away in the node_modules folder.To achieve this, the DevTools team has introduced an extension to source maps, called
x_google_ignoreList. This extension is used to identify third-party sources such as framework code or bundler-generated code. When a framework uses this extension, authors now automatically avoid code that they don't want to see or step through without having to manually configure this beforehand.The
x_google_ignoreListsource map extension is supported by Chrome DevTools starting with Chrome 106.
-
- https://developer.chrome.com/articles/x-google-ignore-list/
-
The ignoreList source map extension
Improve debugging experience in Chrome DevTools with the
ignoreListsource map extension.
-
- https://developer.chrome.com/blog/new-in-devtools-120/#ignore-list-spec
The source maps specification has adopted the
ignoreListfield instead ofx_google_ignoreListand DevTools now supports the new name with a fallback for the old one. Frameworks and bundlers can now use the new field name.Originally posted by @0xdevalias in https://github.com/facebook/react/issues/27774#issuecomment-1836969520
See Also
- https://github.com/facebook/react/issues/27774
- https://github.com/markerikson/react-prod-sourcemaps/issues/19
- https://github.com/vercel/next.js/issues/41370
- https://github.com/vuejs/rfcs/discussions/607
- https://github.com/sveltejs/svelte/issues/9740
- https://github.com/angular/angular-cli/pull/23545
- https://nuxt.com/blog/v3-3#better-logging-in-browser-devtools
- https://vitejs.dev/config/server-options.html#server-sourcemapignorelist
- https://rollupjs.org/configuration-options/#output-sourcemapignorelist
- https://github.com/Rich-Harris/magic-string/issues/241
- Lenguaje dominante
- JavaScript
- Estrellas
- 8.1k
- Forks
- 358
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Guía de contribución
No hay ninguna guía de contribución indexada para este repositorio
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.
Más de developit/microbundle
-
CSS
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
developit/microbundle#1002 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
developit/microbundle#789 · 1 comentario ·
-
Dificultad 3/5 1-2 días Aptitud para principiantes 55/100
developit/microbundle#1100 · 4 comentarios ·
-
Dificultad 4/5 3-5 días Aptitud para principiantes 35/100
developit/microbundle#1094 · 1 comentario ·
-
Disable minification by default Abierto
Dificultad 3/5 1-2 días Aptitud para principiantes 45/100
developit/microbundle#1093 · 3 comentarios · 1 reacción ·
Todos los issues de developit/microbundle
Issues similares
-
awaiting triage bug Causes friction Hop Gui P1 P2 Transforms
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
-
Improve Title Support Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
georgestephanis/p2026#40 ·
-
Enatega Customer and Rider app: Add-ons price is not visible to customer after order is placed. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
Margaret-Petersen/food-delivery-app-clone-react-native#1981 ·