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
A while ago I built a tool to extract information from nodejs.org/dist/index.json. It runs nightly to build data for the static version of the module (the non-static version fetches data from the live site).
In those PRs, over time I've noticed a few bits flip with some regularity - specifically, the security value changes. This could absolutely be an error on my end, but it's complicated to verify that without being able to see the source of truth at the time of execution. I'd be fine to do that, but now I've noticed that the modules versions have started flipping around, too - the modules version on Node.js v20.14.0 flipped from 120 down to 115 - very odd behavior, and I'm guessing that one isn't me.
So, I was hoping that there would be some way to keep a historical log of what's published to that file. If that's just committing it to a repo every time it's changed and I can look at the diff, that's fine. Alternatively, keeping a full version every time it's changed would be nice as well. I'm really down for any solution, I'd just like to be able to see the data historically.
The text was updated successfully, but these errors were encountered:
the modules version on Node.js v20.14.0 flipped from 120 down to 115
115 is the correct number. I have no idea how it could have been 120 before. The lines in that file are not supposed to change, as they are populated from the releases, which are immutable.
Hey!
A while ago I built a tool to extract information from nodejs.org/dist/index.json. It runs nightly to build data for the static version of the module (the non-static version fetches data from the live site).
In those PRs, over time I've noticed a few bits flip with some regularity - specifically, the
security
value changes. This could absolutely be an error on my end, but it's complicated to verify that without being able to see the source of truth at the time of execution. I'd be fine to do that, but now I've noticed that themodules
versions have started flipping around, too - themodules
version on Node.js v20.14.0 flipped from120
down to115
- very odd behavior, and I'm guessing that one isn't me.So, I was hoping that there would be some way to keep a historical log of what's published to that file. If that's just committing it to a repo every time it's changed and I can look at the diff, that's fine. Alternatively, keeping a full version every time it's changed would be nice as well. I'm really down for any solution, I'd just like to be able to see the data historically.
The text was updated successfully, but these errors were encountered: