No indication of cause when dev deployment is broken

[JakobJingleheimer]

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.

[AugustinMauroy]

Wath did you receive on terminal ?

[JakobJingleheimer]

Nothing because I don't run it locally; there's no need to do aside from working around this issue.

[AugustinMauroy]

it's not dev env it's vercel preview right ?

[JakobJingleheimer]

Right. So in vercel, set NODE_ENV to "preview" or something, no?

[AugustinMauroy]

Right. So in vercel, set NODE_ENV to "preview" or something, no?

No, if you do npm run dev on local you I'll get error on your terminal.
If it's a preview of vercel, it's a preview, maybe there's a log on vercel. But I don't have access to that.

[JakobJingleheimer]

Yes, I understand how to get it when running locally, which I never need to do except when the preview deployment blows up and refuses to tell me what's wrong.

An article editor never needs to run things locally—it's just a markdown file. Article editors maybe need not even be technical, so expecting them to install a bunch of deps, get a local up and running, etc is needlessly onerous.

There's got to be a way to capture the error and return it. IIR, this is the default Next.js error page, which is augmentable. In non-prod, even a rsp.send(500, error) would be a big improvement.

[AugustinMauroy]

An article editor never needs to run things locally—it's just a markdown file. Article editors maybe need not even be technical, so expecting them to install a bunch of deps, get a local up and running, etc is needlessly onerous.

I agree with you.

• We had a lack of documentation of which code tabs languages is supported. (that your issue I guess).
• https://github.com/nodejs/nodejs.org/blob/main/apps/site/app/global-error.tsx should handle error that strange.