Repository navigation
Click a component in the browser and open its source in your editor, including
React 19 and current Next.js development builds.
The npm packages are available as 2.0.0 with the latest tag. Chrome and
Firefox extension ZIPs are available as release downloads; the browser-store
updates have not been submitted yet. The Firefox ZIP is unsigned and is intended
for submission or temporary testing, rather than normal installation.
What changed
- Support React 19 and Next.js 15/16, including source resolution for Turbopack
and SWC development builds. - Detect React, Preact, Solid, Vue and Svelte without installing a React DevTools
hook. The extension explains missing development metadata and startup failures. - Navigate component parents, iframes and shadow DOM from the refreshed UI.
- Configure editor destinations, modifier-click bindings and hover actions through
the new settings and onboarding screens. Editor support includes Antigravity
and Neovim (macOS). - Keep site settings isolated and migrate released v1 preferences into the new
settings format. - Support native ESM and CommonJS consumers, with server-safe runtime entry
points. Keep the originallocatorjspackage as a compatibility entry. - Prevent repeated runtime startup and include UI icons in published packages.
Upgrading
The npm packages move from 0.5.x to 2.0.0; browser extensions move from 1.x to
2.0.0. Update the packages used by your integration together:
npm install --save-dev @locator/runtime@2.0.0 @locator/babel-jsx@2.0.0
# Webpack integrations that use the loader:
npm install --save-dev @locator/webpack-loader@2.0.0Configuration now uses a strict shared schema. setup() returns a result;
invalid options return { ok: false, errors } and apply nothing. Editor
destinations use tagged objects such as
{ editor: { kind: "target", id: "cursor" } }. Follow the
configuration migration guide for custom editor
templates, targets and bindings.
Released v1 storage migrates automatically. Unversioned and unreleased preview-v2
storage requires a reset. The extension works on development builds with source
metadata; production builds usually remove that metadata.
Firefox requires version 128 or later. Update the existing Chrome and Firefox
listings so installed users receive the new extension.