Next.js Discord

Discord Forum

[DynamicIO] Project refuses to build after enabling DynamicIO

Unanswered
Brown bear posted this in #help-forum
Open in Discord
Brown bearOP
Hey,

i'd like to incorporate the use cache and cache tag features in my project, but straight after enabling dynamicIO the project refuses to build:

   ▲ Next.js 15.4.0-canary.44
   - Environments: .env
   - Experiments (use with caution):
     ✓ dynamicIO

   Creating an optimized production build ...
 ✓ Compiled successfully in 22.0s
 ✓ Linting and checking validity of types    
 ✓ Collecting page data    
[Error: Route "/_not-found": A component accessed data, headers, params, searchParams, or a short-lived cache without a Suspense boundary nor a "use cache" above it. We don't have the exact line number added to error messages yet but you can see which component in the stack below. See more info: https://nextjs.org/docs/messages/next-prerender-missing-suspense]
Error occurred prerendering page "/_not-found". Read more: https://nextjs.org/docs/messages/prerender-error
Export encountered an error on /_not-found/page: /_not-found, exiting the build.
 ⨯ Next.js build worker exited with code: 1 and signal: null


If i remove the dynamicIO: true, option from next.config.ts, the project builds just fine:
   ▲ Next.js 15.4.0-canary.44
   - Environments: .env

   Creating an optimized production build ...
 ✓ Compiled successfully in 18.0s
 ✓ Linting and checking validity of types    
 ✓ Collecting page data
 ✓ Generating static pages (8/8)
 ✓ Collecting build traces    
 ✓ Finalizing page optimization    

Route (app)                                 Size  First Load JS    
┌ ƒ /                                    56.2 kB         171 kB
├ ƒ /_not-found                             1 kB         102 kB
...
ƒ Middleware                             60.4 kB
ƒ  (Dynamic)  server-rendered on demand


Any clue what I could be missing or is this to be expected with expiremental options. Thanks.

3 Replies

Brown bearOP
Heres my system config:
Operating System:
  Platform: linux
  Arch: x64
  Version: #1 SMP PREEMPT_DYNAMIC Fri May  2 14:06:21 UTC 2025
  Available memory (MB): 31835
  Available CPU cores: 12
Binaries:
  Node: 22.15.0
  npm: 10.9.2
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 15.4.0-canary.44 // Latest available version is detected (15.4.0-canary.44).
  eslint-config-next: 15.2.4
  react: 19.1.0
  react-dom: 19.1.0
  typescript: 5.8.3
Next.js Config:
  output: N/A
@Brown bear Hey, i'd like to incorporate the ``use cache`` and cache tag features in my project, but straight after enabling dynamicIO the project refuses to build: sh ▲ Next.js 15.4.0-canary.44 - Environments: .env - Experiments (use with caution): ✓ dynamicIO Creating an optimized production build ... ✓ Compiled successfully in 22.0s ✓ Linting and checking validity of types ✓ Collecting page data [Error: Route "/_not-found": A component accessed data, headers, params, searchParams, or a short-lived cache without a Suspense boundary nor a "use cache" above it. We don't have the exact line number added to error messages yet but you can see which component in the stack below. See more info: https://nextjs.org/docs/messages/next-prerender-missing-suspense] Error occurred prerendering page "/_not-found". Read more: https://nextjs.org/docs/messages/prerender-error Export encountered an error on /_not-found/page: /_not-found, exiting the build. ⨯ Next.js build worker exited with code: 1 and signal: null If i remove the ``dynamicIO: true,`` option from next.config.ts, the project builds just fine: sh ▲ Next.js 15.4.0-canary.44 - Environments: .env Creating an optimized production build ... ✓ Compiled successfully in 18.0s ✓ Linting and checking validity of types ✓ Collecting page data ✓ Generating static pages (8/8) ✓ Collecting build traces ✓ Finalizing page optimization Route (app) Size First Load JS ┌ ƒ / 56.2 kB 171 kB ├ ƒ /_not-found 1 kB 102 kB ... ƒ Middleware 60.4 kB ƒ (Dynamic) server-rendered on demand Any clue what I could be missing or is this to be expected with expiremental options. Thanks.
Maybe you should create a issue in nextjs GitHub
@Anay-208 | Ping in replies Maybe you should create a issue in nextjs GitHub
Brown bearOP
Alright sounds fair