You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is not our fault if core adds a new file that is expected to be served but does not notify either the build team or the web infra team to ensure that this gets synced over and available 😅 (assuming we did not get reached out as this is the first time Im hearing of this)
The links are working fine? The only one that does not work is the one linking directly to nodejs.org root and that requires some sort of aliasing. Because all doc links or api links are under /doc or /api -- so we should have been requested to at least make this happen 😅
+ what should this alias point towards? The same version available when you do nodejs.org/api?
Activity
AugustinMauroy commentedon Mar 16, 2025
Where did you get this link ? because on nodejs.org we didn't serve that.
cjihrig commentedon Mar 16, 2025
It is linked from this section of the docs: https://nodejs.org/api/cli.html#--experimental-config-fileconfig
AugustinMauroy commentedon Mar 16, 2025
cc @nodejs/web-infra I think this need to be handle by r2/worker ?
maybe point to lasted LTS ?
MattIPv4 commentedon Mar 16, 2025
What generates this file? Is it an artifact of the release process, the API docs build process, something else?
flakey5 commentedon Mar 16, 2025
Yeah I think the worker should be handling this as well, it is part of the release assets https://nodejs.org/dist/v23.10.0/docs/node-config-schema.json.
I'm not sure on how this file is being generated at all, but it does look like a new feature as of 3 days ago.
AugustinMauroy commentedon Mar 16, 2025
node/lib/internal/options.js
Line 40 in 0cfc471
https://github.com/nodejs/node/blob/0cfc471e8288addb6f4d927e8711d507b81e2eeb/tools/doc/generate-json-schema.mjs
ovflowd commentedon Mar 16, 2025
It is not our fault if core adds a new file that is expected to be served but does not notify either the build team or the web infra team to ensure that this gets synced over and available 😅 (assuming we did not get reached out as this is the first time Im hearing of this)
ovflowd commentedon Mar 16, 2025
The links are working fine? The only one that does not work is the one linking directly to nodejs.org root and that requires some sort of aliasing. Because all doc links or api links are under /doc or /api -- so we should have been requested to at least make this happen 😅
+ what should this alias point towards? The same version available when you do nodejs.org/api?
fix: support `/node-config-schema.json`
flakey5 commentedon Mar 16, 2025
I believe so,
/apiis where it's being referenced anywaysmarco-ippolito commentedon Mar 17, 2025
Woopsie 😅 I forgot to ping the web infra team
flakey5 commentedon Mar 18, 2025
This should be fixed now
cjihrig commentedon Mar 18, 2025
Thanks!
ovflowd commentedon Mar 18, 2025
All good! Props to @cjihrig for creating this issue 🙈