


Overview
Click an element on a running Angular, React, Next.js, Vue or Nuxt app, or an HTML page, to open its source line in your editor.
Click any element on a page and open its source code in your editor, at the exact line. Stop searching your project for the component behind a button, a card or a heading. Click it in the browser, and CodeLocator opens the right file at the right line in VS Code, Cursor, Antigravity or IntelliJ IDEA. Nothing to add to your projects. It works with Angular, React (Vite), Next.js, and now Vue and Nuxt apps, with plain HTML pages, and with live sites on staging and production: Angular, React (Vite), Next.js and plain HTML sites (Beta). New in this version - Vue and Nuxt: click an element on a Vue 3 app (Vite or the Vue CLI) or a Nuxt 3 or 4 app running in development, and your editor opens its line in the .vue file. Content you pass into a slot opens where you wrote it, and a click inside RouterLink, NuxtLink or a UI kit component opens the line where your code uses it. - The Value, Styles and Code tabs work for Vue too: Shift+click opens the component's own style blocks (scoped, SCSS, :deep()) or the app's global styles, Ctrl+click opens the refs, computed values and functions the element uses, and Follow the value traces a shown value through props, ref and computed to the fetch, axios or useFetch call. - The bridge (1.0.4) shows a welcome screen in your terminal after npm install -g codelocator: what the install did and what to do next. - Vue and Nuxt picks need bridge 1.0.4. After npm install -g codelocator@latest, press Restart bridge in the side panel if it asks. What you can do - Click: open the element's template, JSX, .vue file or HTML at its exact line. - Shift+click: open the style rule behind it, chosen from every rule that applies, or the line where its Tailwind classes are written. - Ctrl+click: open the code the element uses: the component's TypeScript, its React or Vue handlers and state, or the page script that handles it. - Value, Styles and Code tabs: after a pick, see the element's value, the style rules that apply and the code it uses, each one click away from your editor. - Follow the value: trace a value on the page back to the API call it came from, through inputs, props, fields, services, hooks or page scripts. - Live refresh: save a file and your next pick lands on the new line, with no restart. - Several projects at once: CodeLocator matches each tab to its project. When two projects look alike, it asks once and remembers your choice. - Plain HTML pages: pick on a page served by Live Server or opened from your disk. CodeLocator finds the file by itself, with no path to type. - Time saved: see how many searches CodeLocator saved you this week, with a sentence ready for a report. - Keyboard shortcuts: Alt+Shift+C starts Select, Alt+Shift+K starts Inspect fonts, and Esc stops either one. How it works CodeLocator works with a small companion program, the CodeLocator bridge, that runs on your computer. Install it once with npm install -g codelocator, then run codelocator setup. After an update, press Restart bridge in the side panel. The extension talks to the bridge only at 127.0.0.1, so your pages and your code stay on your computer. Privacy No accounts, no analytics, no tracking. CodeLocator reads a page only after you start a pick or Inspect fonts in that tab. On a staging or production site, CodeLocator asks for your permission once per site and reads only the element you click and its parents. On React and Next.js sites it also reads the page's class names and the names (never the values) of the component props above the element, to find the files on screen. On plain HTML sites it also reads the page's title, ids, the paths of the files it links and short texts of its headings, buttons and links, to find your copy of the page. It never downloads anything from the site, never reads form values, cookies or storage, and you can remove a site at any time in Settings. To find a project or a plain HTML page, the bridge looks in the folders your editor has open or opened recently. For a plain HTML page, it also looks in your Desktop, Documents and Downloads folders. Before it stops an older CodeLocator bridge after an update, it checks that the program on its port is a CodeLocator bridge, and it never stops any other program. Nothing it reads leaves your computer. Requirements Chrome 123 or later or Microsoft Edge, Node.js 20 or later, and one of these: - an Angular, React (Vite), Next.js, Vue or Nuxt app running in development mode (ng serve, vite or npm run dev, next dev, nuxt dev); - an Angular, React (Vite), Next.js or plain HTML site on staging or production, with your copy of the project on your computer, open in your editor or running; - a plain HTML page served by Live Server or a similar tool, or opened from your disk. For pages from your disk, turn on "Allow access to file URLs" for CodeLocator in your browser's extension settings. Inspect fonts needs no bridge and works on any page. Support: https://getcodelocator.com/support
5 out of 58 ratings
Details
- Version1.0.5
- UpdatedNovember 16, 2026
- Size239KiB
- LanguagesEnglish
- DeveloperWebsite
Email
yassin_mohamed310@outlook.com - Non-traderThis developer has not identified itself as a trader. For consumers in the European Union, please note that consumer rights do not apply to contracts between you and this developer.
Privacy
CodeLocator has disclosed the following information regarding the collection and usage of your data. More detailed information can be found in the developer's privacy policy.
CodeLocator handles the following:
This developer declares that your data is
- Not being sold to third parties, outside of the approved use cases
- Not being used or transferred for purposes that are unrelated to the item's core functionality
- Not being used or transferred to determine creditworthiness or for lending purposes
Support
For help with questions, suggestions, or problems, please open this page on your desktop browser