DOM Element to Component Source

A TypeScript library for retrieving the source location of DOM elements in React applications. Perfect for debugging tools, development utilities, and React DevTools extensions.

Features

• 🔍 Source Location Detection - Get the source location of any DOM element in React
• ⚛️ React Framework Support - Works with React 16+ including NextJS
• 🗺️ Source Map Support - Resolves original source locations using source maps
• 🖥️ Server-Side Source Resolution - Resolves source locations from React Server Components using source maps

Installation

npm install dom-element-to-component-source

yarn add dom-element-to-component-source

pnpm add dom-element-to-component-source

Quick Start

Client-Side Usage

import { getElementSourceLocation } from 'dom-element-to-component-source'

// Get a DOM element (e.g., from a click event or querySelector)
const button = document.querySelector('button')

// Extract source location
const result = await getElementSourceLocation(button)

if (result.success) {
  console.log(`Component: ${result.data.componentName}`)
  console.log(`File: ${result.data.file}:${result.data.line}:${result.data.column}`)
} else {
  console.error('Error:', result.error)
}

Server-Side Usage (React Server Components)

import { resolveSourceLocationInServer } from 'dom-element-to-component-source'

// Resolve source location from React Server Components
const serverLocation = {
  file: 'about://React/Server/file:///path/to/.next/server/chunks/ssr/file.js',
  line: 251,
  column: 300
}

const resolved = await resolveSourceLocationInServer(serverLocation)
// resolved.file will point to the original source file (e.g., src/app/components/Intro.tsx)
console.log(`Original source: ${resolved.file}:${resolved.line}:${resolved.column}`)

API Reference

getElementSourceLocation(element, options?)

Retrieves the source location of a DOM element in React applications.

Parameters:

• element: Element - The DOM element to analyze
• options?: SourceLocationOptions - Configuration options

Returns: Promise<SourceLocationResult>

Example:

const result = await getElementSourceLocation(button, {
  maxDepth: 10
})

resolveSourceLocationInServer(sourceLocation)

Resolves a source location that starts with about://React/Server by using source maps to map from server chunk files to original source files. This is particularly useful for debugging React Server Components in Next.js applications.

Parameters:

• sourceLocation: SourceLocation - The source location with a file path starting with about://React/Server

Returns: Promise<SourceLocation> - The resolved source location pointing to the original source file

Example:

const serverLocation = {
  file: 'about://React/Server/file:///path/to/.next/server/chunks/ssr/[root-of-the-server]__abc123._.js',
  line: 251,
  column: 300
}

const resolved = await resolveSourceLocationInServer(serverLocation)
// resolved.file: /path/to/src/app/components/Intro.tsx
// resolved.line: 6
// resolved.column: 7

Note: This function only processes source locations where sourceLocation.file begins with about://React/Server/. If the file path doesn't match this pattern, the original source location is returned unchanged.

Types

interface SourceLocation {
  file: string
  line: number
  column: number
  componentName?: string
}

interface SourceLocationOptions {
  maxDepth?: number
}

type SourceLocationResult = 
  | { success: true; data: SourceLocation }
  | { success: false; error: string }

Requirements

• React 16+ - Required for Fiber node access
• Development Mode - Only works in development mode

Troubleshooting

"This library only works in development mode"

This error occurs when the library is used in production. Make sure you're running your React app in development mode:

# For Create React App
npm start

# For Next.js
npm run dev

# For Vite
npm run dev

"No React Fiber node found on element"

This error occurs when the DOM element doesn't have React internals attached. This can happen if:

1. The element is not rendered by React
2. React is not in development mode
3. The element is from a different React tree

"No debug source information found"

This error occurs when React debug information is not available. Make sure:

1. React is in development mode
2. Source maps are enabled in your build configuration
3. The component was rendered by React

Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

License

MIT © Itay Adler