Because Plunks are refreshed as users update their code, we serve a lot of data on @plnkrco. It's wild to think of how cost-prohibitive it would be to run if not for careful use of cache headers and @Cloudflare. 🤯
@setemiojo@github When I've seen `net::ERR_BLOCKED_BY_CLIENT` in the past, it has generally been that an extension is aborting / rejecting those requests. Any chance you can confirm that you're still seeing the behaviour with all extensions disabled?
@AmyBlankenship@PrettierCode You might have some success by opting into the 'system' runtime by adding the following to package.json:
"plnkr": {
"runtime": "system",
"useHotReload": true
}
I'm working on a MUCH better dependency experience.
@AmyBlankenship@PrettierCode Hi Amy, I guess we need to work on the discoverability for modules! You can add dependencies via Cmd-Shift-P (or via the book icon in the titlebar of a code pane). Hope this helps!
You may notice that preview images for Plunks are rendering with phishing warnings.
This is an unfortunate side-effect of some phishing mitigations and difficulties in upgrading our headless chrome version.
Thank you for your understanding.