3 ms·
I built the browser-sandbox part as a layer of a web-scraping solution that lets you deliver a scraping app anywhere: mobile, desktop, laptop, just using the we
by graderjs 6y ago
I built the browser-sandbox part as a layer of a web-scraping solution that lets you deliver a scraping app anywhere: mobile, desktop, laptop, just using the web and delivering browser UI as a web app.
I didn't use puppeteer in the development, instead working with the raw devtools protocol. This was good, and let me move quickly and deeply understand the internals. As I'm thinking about other ways to monetize this browser tech outside of web scraping, I came across the idea of running puppeteer scripts. I didn't want to go the 'browserless' route of running lots of jobs at scale, for whatever reason, I wanted to focus more on the interface and experience of using something, not just a tool box to run jobs. That's what I was personally interested in and thought could lead to some cool future stuff.
I realized lots of developers use and are passionate about puppeteer, and also that it was a useful "lingua franca" for talking about browser automation and other tasks to do with programmable browsers.
So it just made sense for me to add a puppeteer console to this virtual browser layer to let you automate it and then be able to see it as the automation runs. I envision people can use to help them run and debug their puppeteer creations, as well as just mess around, learn, and maybe even run some sort of regular or high volume tasks.
To that end, I have provided a paid tier, and if you sign up please know that features are still being rolled out, and bugs are being worked out. Because of that I'm offering it at a substantial discount, and if something really isn't working for you yet I'll make sure you're satisfied somehow, or do my best to anyway. :)
Anyway, have a play with it if you're into Chrome, DevTools, puppeteer, especially if you've wanted to pick up these things for a while but didn't really know where to start. Each free browser console has around 10 minutes of life, and there are some limits on memory, cpu and other resources. I've done my best to ensure fair and useful defaults on the free tier, while also preserving the system resources so they can be shared among everyone, and doing my best to prevent abuse. If you can figure out a sandbox escape or a way to bork the system, please engage in responsible disclosure if you do that sort of thing and hit me up with an email at reverse('moc.procysod@sirc')
I apologize for posting again, when my other submission is still on Show. If I could I'd drop the other one off the page. The first submission I posted before I had a few sandbox bugs worked out, and a major bug with Safari on iOS not supporting the new webp image mode I was testing out. I think it probably broke for a lot of people, and in any case, I think it got much less attention that it deserved, maybe simply as a result of the time and tide when I posted, so I'm posting again to see if it earns the attention I think it deserves :)
In future I plan on adding the devtools front-end to each of the browser consoles, sort of in a tab, so you can tab between puppeteer console, devtools front-end, and other tabs to do various "meta tasks" in the browser pane, or browser space.