Website disappears if fetching release info fails

[mohd-akram]

URL:

https://nodejs.org/en/

Browser Name:

Safari

Browser Version:

26.0.1

Operating System:

macOS 15.7.1

How to reproduce the issue:

1. Went to the Node.js website
2. Website to not disappear after a few seconds
3. Website disappears
4. To reproduce:

--- a/apps/site/next-data/generators/majorNodeReleases.mjs
+++ b/apps/site/next-data/generators/majorNodeReleases.mjs
@@ -3,6 +3,7 @@
 import nodevu from '@nodevu/core';
 
 const nodevuData = await nodevu({ fetch });
+if (typeof window !== 'undefined') throw new Error('Poof!');
 
 /**
  * Filters Node.js release data to return only major releases with documented support.

Noticed this while opening the website in the company network which blocks githubusercontent.com.

[MattIPv4]

👀 Looks like https://raw.githubusercontent.com/nodejs/Release/master/schedule.json and https://raw.githubusercontent.com/nodejs/security-wg/main/vuln/core/index.json are both fetched when the site loads. Looks like these come from:

https://github.com/nodejs/nodejs.org/blob/main/apps/site/next-data/generators/majorNodeReleases.mjs
https://github.com/nodejs/nodejs.org/blob/main/apps/site/next-data/generators/vulnerabilities.mjs

@nodejs/nodejs-website why on earth are these generators running client-side when the site is loaded, rather than server-side as the response is generated?

[avivkeller]

Thanks for the bug report! We aren't supposed to even call this API from the client, so if we are, it's definitely not the way we want it work.

Marked as high priority.

[bmuenzenmeyer]

@nodejs/nodejs-website why on earth are these generators running client-side when the site is loaded, rather than server-side as the response is generated?

just a mistake