Docs state that next.config.ts
is supported for both pages and app dir docs but next dev
errors
#70545
-
Link to the code that reproduces this issuehttps://github.com/Ziothh/next-config-ts-example To ReproduceJust start a fresh nextjs project and convert the Current vs. Expected behaviorExpected behaviorDocs state that there is Typescript support but Docs for specific routers: Actual behaviorError printed to console:
Provide environment informationOperating System:
Platform: darwin
Arch: arm64
Version: Darwin Kernel Version 23.4.0: Fri Mar 15 00:19:22 PDT 2024; root:xnu-10063.101.17~1/RELEASE_ARM64_T8112
Available memory (MB): 16384
Available CPU cores: 8
Binaries:
Node: 20.9.0
npm: 10.1.0
Yarn: N/A
pnpm: 8.8.0
Relevant Packages:
next: 14.2.13 // Latest available version is detected (14.2.13).
eslint-config-next: 14.2.13
react: 18.3.1
react-dom: 18.3.1
typescript: 5.6.2
Next.js Config:
output: N/A Which area(s) are affected? (Select all that apply)Documentation Which stage(s) are affected? (Select all that apply)next dev (local), next build (local), next start (local), Vercel (Deployed), Other (Deployed) Additional contextNo response |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
@Ziothh Our documentation mentions that this is only supported in canary versions → https://nextjs.org/docs/app/api-reference/next-config-js#typescript. We should probably add the same mention in the other sections. 🙇🏼 |
Beta Was this translation helpful? Give feedback.
@Ziothh Our documentation mentions that this is only supported in canary versions → https://nextjs.org/docs/app/api-reference/next-config-js#typescript.
We should probably add the same mention in the other sections. 🙇🏼