Replying to @JacobBeckerman
Yep, we’re still alive and working on RunKit everyday!
Replying to @SMJSGaming @kelechsky
Apologies for the delay. We’re having a bit of a hiccup at the moment processing packages. If you’re referring to demangler and std-node, they’re caught in our backlog. Once our issue is resolved we should get through our backlog fairly quickly. I promise we’re not ignoring it :)
Replying to @Tsheeeep
You should see something like this. If not can you check the developer console in your browser and see if there are any errors?
Replying to @fergiemcdowall
The leveldown package includes several different install scripts. For security and correctness reasons RunKit does not support packages that have install scripts. Sorry for the inconvenience.
Replying to @ImagineBananas
Yup, that is your best bet! They’ll also probably want to know about the issue to make things better for future people too.
Replying to @runkitdev @ImagineBananas
If you’re using RunKit in an embed, then whatever site is hosting it. If you’re using RunKit directly, then probably whoever linked you to the document.
Replying to @ImagineBananas
Hi, I believe you want to be reaching out to whatever service us using RunKit, and not us. We just run the code and don’t know about the particular use case you’re using.
Replying to @kgryte
Fwiw, I wasn’t actually able to find any documentation about the behavior when the field is set to false. (Perhaps I missed it?) We looked at the npm source code to verify it.
But supporting all binary packages (and install scripts) is something we’d like to support one day.
Replying to @kgryte
If youre expecting to release a new version of your packages (I noticed most of them tended to be the same version number) then all future versions will be fixed.
We do sometimes reprocess all packages when we make changes, but we try to avoid that given the number: ~23,000,000
Replying to @kgryte
Sorry for the delay and thank you for letting us know about this edge case.
Your package is now available on RunKit.
If you have any more packages that need reprocessing you can DM us that list and I’ll get them reprocessed for you!
This is an area we’ve given a lot of thought to: blog.runkit.com/2017/02/01/s…
Replying to @gr2m @bitandbang
Not only that, since RunKit snapshots the entire state of npm, you can actually freeze the bug forever: so if the test does fail, you can easily rewind to previous package/node version combinations and see what exactly causes: blog.runkit.com/2017/02/01/s…
RunKit retweeted
Using @runkitdev and this gist gist.github.com/tyvdh/c5618b… you could be up and running with smart contracts on @StellarOrg in 30 minutes or less.
Need more details? Check out the Turing Signer Server API docs: notion.so/tyvdh/Turing-Signi…
RunKit retweeted
for #npm or #node users, in case you do not know, you can use the RunKit on the library npm page to test out a library, you do not need to import or download the library, or use code sandbox just to try it out.
I hope this help someone
#javascript #node #programming
RunKit retweeted
Microlink Query Language (MQL) documentation has been revamped.
All the examples are now interactives using @runkitdev.
microlink.io/mql
Replying to @nazar_kulyk
Hi Nazar, yes that is definitely something we’d like to provide. It’s taking us a bit since we’d like to do it in a completely user-controllable way (that way you don’t have to wait for us to “support” the latest typescript).
Replying to @harittweets
Any HTML string will be rendered in the output viewer. So, if you just evaluate a string with a video tag, it should show up.






