Obsolete package showing

No problem, it was showing already for couple of months before. Thank you

Same here https://npm.runkit.com/set-immediate-interval, latest 1.1.5, uses 1.1.4

I have the samme issue with https://npm.runkit.com/ac-keijiban. It shows 1.0.2 when the last version is 1.2.0.

I have the same issue with timezone-support. It seems to be stuck with 1.8.1, although the newest is 2.0.2

How often does RunKit synchronise their module database with the NPM registry?

Hey everyone,

Right now it appears npm’s skimdb, which we use to get package updates, is currently down:

Sorry about the issues!

We’ll update you when we have more information.

- Randy

Any update on this? I’m facing the same issue. Package version not updated even I published on NPM.

otiai, it seems like you’ve found a new case of a very old thread (the previous post on this thread was from 2017!)

Sometime in November 2023, I and others observed that new packages and package versions uploaded to NPM stopped being updated on RunKit. I don’t believe this project is being actively maintained anymore, though it would be delightful if that changed.

(For what it’s worth, I’ve found that val.town, a project I don’t have any personal connection to, has been a reasonable replacement for the sorts of things I used to use RunKit for. Here’s an example of a little code snippet I would have used runkit to demonstrate in the past.)