nodejs / nodejs/release-cloudflare-worker

Serve the Release/schedule.json file from the website

Open
#904 4 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
57
Forks
21
Avg merge
3d 8h
Merged PRs (30d)
19

Description

Right now, my package nodevu relies on Release/schedule.json to enrich Node.js version data. This information - even if inaccurate or unreliable! - is very helpful at enriching dist/index.json into a more end-user friendly API.

I'd really love it if this information was available on the website directly, even if put in an experimental/untrusted/unreliable position (/dist/DONOTUSE/schedule.json, /untrustworthy/schedule.json, etc.). In talking with @ovflowd, apparently nodejs.org's usage of nodevu does sometimes get rate limited by GitHub because it's hitting this file frequently enough.

I recall that in the past @nodejs/release has been hesitant to provide a contract for this file. I'd be 100% okay with taking on the maintenance burden of having breaking changes be unannounced and fully reliant on consumers with no commitment from @nodejs/release. Having it on the website would just be really nice.

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.

Research direction

Start by tracing how the website serves dist/index.json and review the source Release/schedule.json, including the proposed URL options in the issue. Done means the schedule data is available from the website at an agreed path, with its experimental or unreliable status made clear to consumers.

Written by the indexing model from the issue text.

Assessment

Tech stack
node.js, typescript
Domain
infrastructure, release
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
58/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.