Does global-error.js work in static exported apps?

[gndelia]

Summary

I have an app that uses the App router, and it is exported as a static page. It uses output: 'export', in its next.config.js. This app is deployed in Hostinger, let's say in page.com. It uses an .htaccess for any route configuration needed.

There are several routes, all work well. However, when accessing page.com//, the whole app breaks.
If I serve the app locally using serve, entering localhost:3000// does not break - it gets normalized into localhost:3000. It seems that serve runs some kind of URL normalization, which does not happen in Hostinger. But I'm ok with that.

The issue is that when the app crashes, I'd expect the page to render the global-error.tsx, but this is not happening. Nothing gets rendered - just a blank page. Chat GPT says that global-error.js only works for SSR environments, but I couldn't find anything like that in the docs. It is not mentioned either in the docs of Unsupported features for the Static Export

Does the global-error.tsx work in a static page using the App Router? If not, what alternative do I have for "Catch-all" errors?

Additional information

The next version is `14.2.16`. 
The React version is `18.2.0`

From what I could gather from the minified bundle, this is where the page breaks


let e = new URL("" + p.pathname + p.search,p.origin), t = [["", l, null, null]];
(0,
 i.createPrefetchCacheEntryForInitialLoad)({
    url: e,
    kind: s.PrefetchKind.AUTO,
    data: [t, void 0, !1, m],
    tree: E.tree,
    prefetchCache: E.prefetchCache,
    nextUrl: E.nextUrl
})


Here, `p.pathname` is `//`, so it generates an invalid URL, causing an error to be thrown. It seems this is part of the Next source code, but I was unable to map this into the next's source code

If you need to check the repo where this problem is happening, you can check [the source code](https://github.com/hemilabs/ui-monorepo/tree/dea586d7c63fc403f614b371e2a5ab39cd5bbf6d/portal)

Example

No response

[icyJoseph]

Works for me, with Next 14.2.16

Strange, could, Hostinger be doing something to the URL, rewrite/redirect kind of thing?

[gndelia]

I tried using npx serve out -s and it still redirects just fine. serve version is 14.2.4

[gndelia]

ok, I think the browser was tricking me! I just tried on chrome and it indeed crashes (although no global-error.tsx page).

However, in Brave, The URL gets normalized and the page loads normally (Redirecting to localhost:3000

So

• Brave was doing the URL normalization, not serve
• Regardless, the global-error.tsx page does not load :/

[gndelia]

ok, now I've simplified my global-error page with a simple "Error" text and it worked. So there must be a small error in the global-error.tsx page that prevents it from rendering. I will troubleshoot that.

So the answer is to the question of the discussion is:

Yes, global-error.tsx does work in static pages

[icyJoseph]

TIL, Brave does some funky stuff 🤔 I wonder what their motivation is ~ maybe it is part of an additional security layer they have? interesting

[gndelia]

Yeah, indeed it was unexpected. And as it is my primary browser for development, I did not think of testing in another browser.

Regardless, thanks for your help and time!