25d34057d6
x-ref: #38750 x-ref: https://github.com/vercel/next.js/pull/38750#discussion_r926203439 cc @ijjk The PR implements the details about un-extractable fields in the `UnsupportedValueError`. The PR also enhances the warning message about the unrecognizable `config` field. Now the warning message will look like this: ``` warn - Next.js can't recognize the exported `config` field in route "/unsupported-value-type": Unsupported node type "CallExpression" at "config.runtime". The default config will be used instead. Read More - https://nextjs.org/docs/messages/invalid-page-config ``` The corresponding production test case has also been updated. |
||
|---|---|---|
| .. | ||
| extract-const-value.ts | ||
| get-page-static-info.ts | ||
| parse-module.ts | ||