denoland / denoland/deploy_feedback
[Bug]: 500 Internal Server Error on domain where Nextjs project was "successfully" deployed to
- Dominant language
- No language data
- Stars
- 79
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
### Problem description
The deployment went ok with Github Actions, but the URL where it is deployed instantly gives a blank page with 500 Internal Server Error.
The Deno logs do show:
```
TypeError: Cannot read properties of undefined (reading 'clientModules') at eventLoopTick
```
but I don't get this locally, where everything works fine, both in dev, as well as with `next build`.
It is hard to debug this, since Deno does not provide much further info to go on.
The public repo is [here](https://github.com/davidde/ethblox).
### Steps to reproduce
1. git clone https://github.com/davidde/ethblox
2. Deploy to deno with automated setup process.
3. Browse to deployed project and see 500 Internal Server Error.
### Expected behavior
I expect to see the same I see in local builds, i.e. a functional website.
### Environment
_No response_
### Possible solution
_No response_
### Additional context
_No response_
Contributor guide
No contributing guide indexed for this repository
Research direction
Clone the linked ethblox repository, inspect its GitHub Actions automated deployment setup, and compare the local `next build` result with the deployed Deno runtime. Use the reported Deno `clientModules` error and deployed URL as the starting checks; done means the deployed site loads successfully instead of returning HTTP 500.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- deno, github-actions, nextjs
- Domain
- cloud, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100