@Tsheeeep Can you go to chrome://flags and see if you have the throttle iframes option enabled: chrome://flags/#enable-throttle-display-none-and-visibility-hidden-cross-origin-iframes
@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 :)
@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.
@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.
@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.
@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.
@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
@NeverwinterMoon Sorry about that. We’re actively working on upgrading our infrastructure right now to support new syntax features. (Sadly, it’s been something we’ve neglected for too long)
You can read a little more about it here: https://t.co/UOS2mOZdLL
@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: https://t.co/g2yCdieQTl
Using @runkitdev and this gist https://t.co/i68bbyuKlc 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: https://t.co/bqxTHSFDxM
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
@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).