No indication of cause when dev deployment is broken

Open
#7,464 15 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
nextjs, typescript
Domain
web-dev

Research direction

Start by reproducing the failure at the reported URL in the development deployment, then trace the page-generation error handling and the response that produces the 500. Done means non-production responses expose the triggering error while production behavior remains appropriate; the payload names no files or tests to inspect.

Written by the indexing model from the issue text.

Description

help wanted
URL:

https://nodejs-5gs7cwzc2-openjs.vercel.app/en/learn/typescript/publishing-a-ts-project

Browser Name:

Brave

Browser Version:

1.73.105

Operating System:

macOS

How to reproduce the issue:

When a page can't be generated, the server returns a 500 with no information whatsoever for what went wrong. In a non-production environment, it should include the error that triggered the 500.

Shit happened. Good luck
Dominant language
TypeScript
Stars
6.9k
Forks
6.5k
Avg merge
2d 9h
Merged PRs (30d)
29

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from nodejs/nodejs.org

All issues in nodejs/nodejs.org

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.