Hữu ích lắm, ủng hộ team 5Sao để phát triển thêm nha
Local UI Source Inspector
- 48 users
- 5.009 ratings
- #8,850in Developer Tools
Inspect local Vite UI source, matched CSS, and JS listeners, then copy context for Codex or open files in VS Code.
by VNI · 1 listing
- Users
- 48
- #8,850 of 31,410 in category
- Rating
- 5.00
- 9 ratings · median 4.63
- Version
- 0.2.33
- 76.53 KiB · Manifest V3
- Access
- Low15/100
- 3 permissions + 3 site patterns
Description
As written by the publisher on the storeLocal UI Source Inspector helps frontend developers trace a selected UI element in a local Vite application back to its authored source.
HOW TO USE
- Install vite-plugin-react-source-locator in the target Vite project.
- Copy the configuration for your framework from the built-in Detailed Guide.
- Restart the Vite development server.
- Open the local application and enable Inspect Mode.
- Hover over an element to highlight it, then click to pin its source information.
MAIN FEATURES
- Inspect UI elements on localhost, 127.0.0.1, and [::1]
- Show the detected component, template, or HTML source location
- Display file path, line, column, and rendered dimensions
- Highlight and pin elements, including multi-selection with Shift/Ctrl-click
- Show matched authored CSS, CSS Modules, and inline styles
- Map SCSS, Sass, and Less when usable Vite development source maps are available
- Show supported JavaScript and TypeScript listener locations when available
- Copy selected source context
- Copy a structured prompt for an AI coding assistant
- Open validated absolute Windows source paths in VS Code
- English and Vietnamese interface and documentation
VERIFIED COMPATIBILITY
Vite is currently the only tested and proven build-tool integration.
- Full verified workflow: Vanilla Vite, CSS, CSS Modules, and inline styles
- Main component/template workflow: React, Preact, Solid, Vue 3, Svelte 5, and static Astro components
- Main styling workflow: SCSS, Sass, Less, and Tailwind component/template source
KNOWN LIMITATIONS
- Compiler-managed events in Vue, Svelte, and Astro may have partial source tracing
- Astro Islands are not fully verified
- Generated Tailwind utility CSS is not treated as an editable authored CSS file
- Next.js, Angular, Nuxt, Webpack, and Turbopack are not official source-tracing integrations
- Open in VS Code currently requires an absolute Windows drive path and may reuse the current VS Code window
PRIVACY AND LOCAL PROCESSING
Inspection is restricted to local development pages served over HTTP from localhost, 127.0.0.1, or [::1].
The extension processes inspected page content and source-location metadata locally on the user's device. It does not upload source code, inspected DOM content, or copied context to external servers. It contains no analytics, telemetry, advertising, or external API requests.
Only Inspect Mode and language preferences are stored in Chrome local extension storage. Source files and production builds are not modified.
Ratings and reviews
Split of the 5 written reviews we hold5 written reviews we hold
Track Local UI Source Inspector on Radar
This page shows the listing as it is today. Add it to Radar and get one email when it changes.
- Users and rating
- Store text and screenshots
- Permissions it asks for

Local UI Source Inspector, in plain words
What it is, what to use instead, what it can access and how to fix it.
Local UI Source Inspector at a glance
Local UI Source Inspector is a Developer Tools extension by VNI with 48 users. Chrome Web Store users rate it 5.00 out of 5 from 9 ratings, which is still a small sample. By users it sits in the top half of Developer Tools extensions.
- By users
- #8,850of 31,410 in Developer Tools
- Rating
- 5.00category median 4.63
- Access
- Low15 of 100
Local UI Source Inspector alternatives
Closest by what they do · users as the store shows them · bars on a log scaleIs Local UI Source Inspector safe?
Local UI Source Inspector asks for 3 permissions and access to 3 site patterns. None of them are on our list of wide-access permissions.
Permissions show what it could do, not what it does. See the full permission list.
activeTabNot on our wide-access listclipboardWriteNot on our wide-access liststorageNot on our wide-access list
Every permission Local UI Source Inspector asks for
3 permissions + 3 site patterns · none sensitive · Low access overallSites
- Read and change data on matching sites
http://localhost/* - Read and change data on matching sites
http://127.0.0.1/* - Read and change data on matching sites
http://[::1]/*
Browser permissions · 3
- Work on the tab you click it on
activeTab - Copy text to your clipboard
clipboardWrite - Save its own settings
storage
Sensitive marks access that reaches your data or other sites. The access level is a 0 to 100 score of all of it: under 25 is Low, 60 and up is High.
Local UI Source Inspector not working?
What recent reviews say
Store reviews from the last 90 daysCommon fixes
Try them in this order- 1Update Chrome and the extension
- 2Turn it off and on in chrome://extensions
- 3Reload the page
- 4Turn other extensions off in case two clash
Still stuck? Contact the maker or try an alternative.
Know when a listing changes
Track any extension on Radar: users, rating, permissions and store text, with one email when something moves.