Add `x_google_ignoreList` (Ignore-listing code) support to sourcemaps
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Idoneità per principianti
- 35/100
- Tipo di issue
- Funzionalità
- Chiarezza
- Abbastanza chiara
- Stato di attività
- Ferma
- Stack tecnologico
- javascript, rollup
- Ambito
- build-system
Direzione di ricerca
L’issue non indica file, test o punti di ingresso. Inizia tracciando come microbundle delega la generazione delle sourcemap a Rollup, quindi confronta le mappe generate con la source-map ignoreList specification. Il lavoro è completato quando le sourcemap generate identificano le sorgenti di framework o dipendenze tramite il campo ignore-list richiesto, con copertura per i percorsi di output pertinenti.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
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
- Lingua principale
- JavaScript
- Stelle
- 8.1k
- Fork
- 358
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Guida per i contributori
Nessuna guida per i contributori indicizzata per questo repository
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di developit/microbundle
-
CSS
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
developit/microbundle#1002 ·
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
developit/microbundle#789 · 1 commento ·
-
Difficoltà 3/5 1-2 giorni Idoneità per principianti 55/100
developit/microbundle#1100 · 4 commenti ·
-
Difficoltà 4/5 3-5 giorni Idoneità per principianti 35/100
developit/microbundle#1094 · 1 commento ·
-
Difficoltà 3/5 1-2 giorni Idoneità per principianti 45/100
developit/microbundle#1093 · 3 commenti · 1 reazione ·
Tutte le issue di developit/microbundle
Issue simili
-
awaiting triage bug Causes friction Hop Gui P1 P2 Transforms
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
-
Improve Title Support Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 70/100
georgestephanis/p2026#40 ·
-
Enatega Customer and Rider app: Add-ons price is not visible to customer after order is placed. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
Margaret-Petersen/food-delivery-app-clone-react-native#1981 ·