Replies: 6 comments 6 replies
-
Are you able to build the application locally or does it just exit? I found that when I specified webpack config in next.config.ts file it would prevent next build from outputting anything. Wonder if you're having the same issue. |
Beta Was this translation helpful? Give feedback.
-
It works very well when I run |
Beta Was this translation helpful? Give feedback.
This comment was marked as off-topic.
This comment was marked as off-topic.
-
@yunsii I noticed your file extensions are set to Is there a reason why you are suffixing your files this way? |
Beta Was this translation helpful? Give feedback.
-
Same problem
with custom page extension |
Beta Was this translation helpful? Give feedback.
-
It is worth mentioning that my project deployed successful after I removed |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Link to the code that reproduces this issue
https://github.com/yunsii/awesome-exhibition
To Reproduce
Current vs. Expected behavior
Throw error:
Provide environment information
Operating System: Platform: linux Arch: x64 Version: #1 SMP Fri Mar 29 23:14:13 UTC 2024 Available memory (MB): 15896 Available CPU cores: 12 Binaries: Node: 18.19.0 npm: 10.2.3 Yarn: N/A pnpm: 8.13.1 Relevant Packages: next: 15.0.2-canary.7 // Latest available version is detected (15.0.2-canary.7). eslint-config-next: N/A react: 18.3.1 react-dom: 18.3.1 typescript: 5.3.3 Next.js Config: output: N/A
Which area(s) are affected? (Select all that apply)
Not sure
Which stage(s) are affected? (Select all that apply)
Vercel (Deployed)
Additional context
No response
Beta Was this translation helpful? Give feedback.
All reactions