fix(shims): import local navigation module in error boundary

[NathanDrake2406]

Summary

The built package can execute shims/error-boundary.tsx before the plugin's resolveId hook is active, so the public next/navigation alias is not yet registered. Import the local ./navigation.js module directly instead.

Three-line change extracted from the PR #768 restack; landing independently because it's orthogonal to the layout-persistence feature work.

Stack context

This is the sibling of the PR #768 restack. Not part of the 6-PR stack; open on its own.

Test plan

• vp check on the shim file
• Manual verification in examples/ that the error boundary still renders when thrown

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/vinext@837

commit: 21894a0

[Copilot]

Pull request overview

This PR fixes early-execution failures in the built error-boundary shim by avoiding the next/navigation public alias (which may not be registered yet) and importing the local navigation shim directly.

Changes:

• Replace next/navigation import with a direct relative import from ./navigation.js in the error boundary shim.
• Remove the lint suppression comment that was only relevant to the aliased import.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[james-elicx]

/bigbonk review

[ask-bonk]

LGTM. This is a straightforward and correct fix.

error-boundary.tsx was the only shim file still importing from the public next/navigation alias — every other sibling (link.tsx, slot.tsx, form.tsx, layout-segment-context.tsx, navigation-state.ts, navigation.react-server.ts) already uses ./navigation.js. This aligns the outlier and eliminates the race where the built package executes the shim before the plugin's resolveId hook is active.

The removed oxlint-disable-next-line comment is no longer needed since the direct relative import is a standard ESM import, not a shimmed alias.

[ask-bonk]

Approved the PR. The change is correct and consistent with the rest of the codebase:

• error-boundary.tsx was the only shim still importing from the public next/navigation alias. All 7 other sibling shims already use the direct ./navigation.js relative import.
• The fix eliminates a real race condition where the built package could execute the shim before the plugin's resolveId hook registers the next/navigation alias.
• The oxlint-disable-next-line suppression is correctly removed since the direct import doesn't trigger that lint rule.

github run