Summary

• Adds a server-side cache mapping (fileName, line, column) → AST nodePath to handle stale source maps after suppressed webpack rebuilds
• When prettier reformats a file (e.g. wrapping a return in parentheses), JSX tags shift lines. The stale source map still resolves to the old line, but the cached nodePath remains valid since the AST structure is unchanged
• Cache is cleared on compiler.hooks.done when webpack rebuilds and source maps become fresh again

Problem

// Before — source map says <Video> is on line 22:
export const Component = () => {
  return <Video src={src} />;      // line 22
};

// After adding style={{}} + prettier wrapping — tag moves to line 23:
export const Component = () => {
  return (
    <Video src={src} style={{}} />  // now line 23
  );
};

On reload, the stale source map still resolves to line 22, but lineColumnToNodePath(ast, 22) finds nothing → subscribe-to-sequence-props fails.

Solution

1. On first successful subscription: cache (file, line, col) → nodePath
2. On subsequent requests with stale coordinates: reuse cached nodePath (verified against current AST)
3. On webpack rebuild: clear cache (source maps are fresh, line-based lookup works)

Test plan

• Added e2e test in packages/example/e2e/node-path-cache.test.mts that verifies the cache handles line shifts
• Existing visual controls and undo-redo e2e tests still pass
• Manual test: open studio, edit a component to trigger prettier reformatting, reload — sequence props controls still work

🤖 Generated with Claude Code