First-time navigation breaks in dev if destination page has a lazy import with decorators

### Link to the code that reproduces this issue https://codesandbox.io/p/devbox/vibrant-http-r4kcq9 ### To Reproduce 1. Restart dev server 2. Load homepage 3. Click link, new page will momentarily load, then bounce you back to the homepage 4. Click link again and new page will load as expected ### Current vs. Expected behavior I expect the link to work on the first attempt ### Provide environment information ```bash Operating System: Platform: linux Arch: x64 Version: #1 SMP PREEMPT_DYNAMIC Sun Aug 6 20:05:33 UTC 2023 Available memory (MB): 4102 Available CPU cores: 2 Binaries: Node: 20.11.1 npm: 10.2.4 Yarn: 1.22.19 pnpm: 8.15.4 Relevant Packages: next: 14.2.1 // There is a newer version (14.2.4) available, upgrade recommended! eslint-config-next: 14.2.1 react: 18.2.0 react-dom: 18.2.0 typescript: 5.4.5 ``` ### Which area(s) are affected? (Select all that apply) Developer Experience ### Which stage(s) are affected? (Select all that apply) next dev (local) ### Additional context I've investigated this quite a bit as it affects us everyday. The two compounding causes are: 1. Using decorators on a subset of pages, this means the swc/helper for decorators isn't initially added to the bundle 2. Using a lazy import (next/dynamic) seems to cause the dependency order in the `pages/_document` bundle to change, resulting in the bundle hash changing and a page reload being forced. With a static import, the dependency order is stable, so the issue isn't triggered. I've managed to work around this locally by patching Next to not externalise the swc helpers, but obviously would prefer not to have to maintain a patch and/or give up the optimisation.