Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Output export and distDir in the config file will crash the dev server (Ver 14.1) #61905

Closed
leo-budgetsimple opened this issue Feb 11, 2024 · 5 comments
Labels
bug Issue was opened via the bug report template. locked

Comments

@leo-budgetsimple
Copy link

Link to the code that reproduces this issue

https://github.com/leo-budgetsimple/nextjs-bug

To Reproduce

Copy over the repo

Start the application on dev (npm run dev)

Go to localhost:3000

You should see the text 'Hello'

but instead you get:
missing required error components, refreshing...

Current vs. Expected behavior

Current Behavior:

Cannot run development server, this error appears on the screen:

missing required error components, refreshing...

Expected Behaviour

To be able to run the dev server.

Provide environment information

Operating System:
  Platform: linux
  Arch: x64
  Version: #15~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Jan 12 18:54:30 UTC 2
Binaries:
  Node: 18.19.0
  npm: 10.2.3
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 14.1.1-canary.47 // Latest available version is detected (14.1.1-canary.47).
  eslint-config-next: N/A
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.1.3
Next.js Config:
  output: export

Which area(s) are affected? (Select all that apply)

Static HTML Export (output: "export")

Which stage(s) are affected? (Select all that apply)

next dev (local)

Additional context

This happened after I upgraded to NextJs 14.1.

Doesn't happen with old versions.

If I remove distDir the dev server works as intended, same as if I remove the output: export

@leo-budgetsimple leo-budgetsimple added the bug Issue was opened via the bug report template. label Feb 11, 2024
@leo-budgetsimple leo-budgetsimple changed the title Output export and distDir in the config file will crash the dev server Output export and distDir in the config file will crash the dev server (Ver 14.1) Feb 11, 2024
gregorbg added a commit to gregorbg/scrambles-matcher that referenced this issue Feb 15, 2024
gregorbg added a commit to gregorbg/scrambles-matcher that referenced this issue Feb 15, 2024
gregorbg added a commit to gregorbg/scrambles-matcher that referenced this issue Feb 15, 2024
gregorbg added a commit to gregorbg/scrambles-matcher that referenced this issue Feb 15, 2024
gregorbg added a commit to gregorbg/scrambles-matcher that referenced this issue Feb 15, 2024
gregorbg added a commit to gregorbg/scrambles-matcher that referenced this issue Feb 15, 2024
gregorbg added a commit to gregorbg/scrambles-matcher that referenced this issue Feb 15, 2024
@drmahikbov
Copy link

Would love to have some feedback, I got the same problem on my frontend react strapi website

@atstoyanov
Copy link

I have the same issue the dev server is looking for build/server/middleware-manifest.json instead of .next/server/middleware-manifest.json

@KevenGoncalves

This comment has been minimized.

@ijjk
Copy link
Member

ijjk commented Feb 23, 2024

Closing as this is fixed in latest canary of Next.js, x-ref: #61105 (comment)

@ijjk ijjk closed this as completed Feb 23, 2024
dguo added a commit to dguo/make-a-readme that referenced this issue Feb 23, 2024
dguo added a commit to dguo/make-a-readme that referenced this issue Feb 27, 2024
Keep Next.js on 14.0.0 instead of 14.1.0 because of a dev
server crashing issue:
vercel/next.js#61905
Copy link
Contributor

github-actions bot commented Mar 9, 2024

This closed issue has been automatically locked because it had no new activity for 2 weeks. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.

@github-actions github-actions bot added the locked label Mar 9, 2024
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 9, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue was opened via the bug report template. locked
Projects
None yet
Development

No branches or pull requests

5 participants