Electron VS puppeteer

Repository: Electron

Electron GitHub Repository

The team at Electron have been faithfully shipping new releases almost every single month. I think they had Christmas off 🤔. This popular framework has developers writing cross-platform desktop applications using JavaScript, HTML and CSS. The latest update depreciates some process events, and added new modules, APIs, methods, and more. Read into all the changes in the Electron release notes. This month, Electron also introduced a new formal RFC process.

VS Code has been crashing at launch in Wayland since more than eight months ago:

https://github.com/electron/electron/issues/37531

So we talked a lot about the Atomic Design Principle, but you could just use that in any system and start creating. You could have Angular components, React Components, and Vue Components. But if you notice these don't easily work Everwhere. So the solution is to use Web Components because the modern browser can already understand these, and any Front-End framework can then utilize these components. You can use Electron for desktop (Slack, VSCode), PWA for both Android and iOS, and across all browsers Can I Use.

I'm noticing a significant boost in performance, crisper text, and better power savings. The only shortcoming is that the window which Figma will run on will lose its shadow. This is due to a technical limitation with frameless windows on Linux.

For the longest time, building desktop apps was a daunting task to web developers. That is, until technologies like Electron made creating these apps more approachable to a wider audience. Today, we’ve got a wide array of native applications built with solutions like Electron, Tauri, Capacitor, and many more. While these are great solutions, sometimes configuration can be tricky and the applications we create can become somewhat bloated in terms of memory usage.

Electron patch for version 27: https://github.com/electron/electron/pull/39823

You could probably do it using something like Puppeteer [0].

[0]: https://pptr.dev/

Puppeteer

Just as described on the docs

Execution context was destroyed, most likely because of a navigation #3323

"page.waitForXPath is not a function" in 22.10.0

For more information, you can refer to the Puppeteer Documentation and BeautifulSoup Documentation.

I had to write my JavaScript code to display the visitor count on my resume, utilizing the call to my API. To do that, I also had to set up an API gateway to my lambda function. After this, I wrote some tests in Python to make sure my API was working properly. I wrote unit tests, integration tests, and end-to-end tests. I had some experience in Selenium, so this time, I chose to try out puppeteer, doing something new.

To my surprise the code was closer in structure to the puppeteer version than it was to the chromedp. The chromedp version uses nested context declarations to manage the browser and page runtimes, the rust version uses a more linear approach. You construct a browser instance and then you can interact with it as a user would. This points at the fact that the chromiumoxide api is higher level.

In this tutorial, we can extract data from the HTML structure, so we will go with Cheerio, but for extracting data from SPAs or JavaScript-rendered websites, Crawlee also supports headless browser libraries like Playwright and Puppeteer