mirror of
https://github.com/vercel/next.js.git
synced 2026-09-20 02:25:18 +08:00
Niklas Mischkulnig
85ef3638b3
Metadata routes are just `route.ts`\-s in diguise. Treat them the same regarding the layer (`app-route`) and whether to emit client reference/server actions manifests for them (= don't). This fixes a panic: ``` thread 'tokio-runtime-worker' panicked at crates/next-api/src/dynamic_imports.rs:70:26: called `Option::unwrap()` on a `None` value note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace ``` https://vercel.slack.com/archives/C05TH5T3DS8/p1755670936074369
6 lines
127 B
JavaScript
6 lines
127 B
JavaScript
'use client'
|
|
|
|
import dynamic from 'next/dynamic'
|
|
|
|
export const DynamicComponent = dynamic(() => import('./dynamic-component'))
|