Npm package updates


i try to create a runkit using but it is not using the latest published version… the runkit search gives me version 0.0.1 while i published v0.0.3 yesterday… does it have anything to do with only updating the PATCH version digit? do i need to update the minor version as well?

Regards, Pattrick

1 Like

Same problem here (
The library is on 1.1.51 while the RunKit example shows 1.1.39
Where does RunKit get its version from?

Hm… after several days version 0.0.3 started appearing… to actually use it, i had to copy my runkit code into a new runkit, the old one still had the old version…
When i updated my dependency to 0.1.0 (minor version update) the new version appeared much quicker than the patch level update before

Hi phueper,

The way RunKit notebooks work is that they are locked to the original version of the package they use. That way, if you return to a notebook a day later, running it wouldn’t accidentally get you a different package. In order to “reset” it and get the latest package, you can delete the reference to it, run, and then add it back in. This isn’t ideal we know, but we are working on better UI to make it more reasonable.

Sorry for the confusion!



Any progress on this, francisco? it is quite unintuitive…

Hi Dthowe,

Rita shows 0.1.391 since that is the latest version. I believe you intended 391 to be “in-between” 0.1.39 and 0.1.40, but the way semver works, it actually means 391 is LARGER than anything else *the same way that 0.1.51 is larger than 0.1.6). An easy fix would be to publish to 0.2.0.

Let me know if you need any other help!

1 Like

Sorry, I think the version you intended to write was 1.1.39 (we are currently at 1.1.51) – can you update/clarify?

Currently, our NPM pages show the largest semver version. At some point version 1.1.391 was published, and that is larger than 1.1.51.

We’ve deleted the 1.1.391 from npm, however it still shows up in runkit. Is there some cache that can be cleared?

Yeah, currently there is no automatic process for removing versions of packages. I’ve gone ahead and removed v1.1.391 for you. Version 1.1.60 should now be showing up in our NPM page for Rita. Sorry about the confusion!

  • Randy


I’ve updated a package to 1.0.1 but runkit shows version 0.0.0

Why doesn’t runkit show current version?
How can I fix this?


The package is now available!

– Randy

1 Like

Thanks Randy, you’re awesome!

Facing the same problem of runkit serving an older version at
I think this is a very big problem and something should be done about it quickly. I realized it’s something general. Our won’t correlate with the response from runkit. And hence, developers will think the packages aren’t working. Please help

Hi doc-han,

Sorry for the delayed reply, I thought I had already replied, but I guess not.

IIRC, your package appeared on RunKit about an hour after you made this post. There’s some period time before packages are available, but generally it shouldn’t take that long. We’re looking into the logs to try and figure out why.

Sorry for the inconvenience,
- Randy

Okay me1000,
But this time around I updated to version 1.1.9 like 3days ago and it’s still stuck at version 1.1.8

Unfortunately you’ve caught us at a bad time :slight_smile:

Due to some changes npm made out of our control we’ve got a backlog for a few hundred thousand packages we need to process. This post has a bit more detail: New packages and versions not showing up

I’ll update this thread when we believe things are back to normal.

- Randy

Hi all,

We’ve finished processing the backlog of the packages mentioned in the previous thread.

If you run into any other issues, please don’t hesitate to let us know.

Again, we’re sorry for the inconvenience.

- Randy