Electron VS cheerio

Compare Electron vs cheerio and see what are their differences.


:electron: Build cross-platform desktop apps with JavaScript, HTML, and CSS (by electron)


Fast, flexible, and lean implementation of core jQuery designed specifically for the server. (by cheeriojs)
Our great sponsors
  • Nanos - Run Linux Software Faster and Safer than Linux with Unikernels
  • Scout APM - A developer's best friend. Try free for 14-days
  • SaaSHub - Software Alternatives and Reviews
Electron cheerio
112 18
99,167 24,559
0.5% 0.5%
9.9 9.6
about 16 hours ago 1 day ago
C++ TypeScript
MIT License MIT License
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.


Posts with mentions or reviews of Electron. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-11-25.


Posts with mentions or reviews of cheerio. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-11-29.
  • Automating email verification for online accounts using JavaScript
    6 projects | dev.to | 29 Nov 2021
    cheerio to parse the HTML structure of an incoming email and filter out the link we need to click to verify our email address by an attribute (in this case the text Content of the link but it could be any html attribute)
  • In-lining Styles Client Side
    7 projects | dev.to | 11 Nov 2021
    And it in-lines tagged HTML wonderfully. Works well.

    Still, it's overkill, brings with it dependencies cheerio, mensch and slick and a look into the code behind the on-line demo makes rapidly clear that Juice is parsing the style sheets and applying them in what looks to be, must be, a product of its age. It has over 1500 lines of Javascript and the repo was created in 2011 - the state of Javascript was woeful then compared with today (though not as woeful as in 2001 ๐Ÿ˜).

    So we have to give Juice full credit and admiration for its age and endurance, and that it's still being maintained and is useful. But I'll respectfully pass it by as I'm looking for a minimalist, native Javascript solution as far as possible, using the state of Javascript in 2021 a whole decade later (which in IT terms is an eon).

    inline-css ๐Ÿ‘Ž

    Immediately disconcerting is the npm documentation for this package. It says simply "Inspired by juice" and fails to tell us why the authors felt that embarking on a new project was worth their while. It hints at the fact that it's better than Juice in some way or other (why else start a new project inspired by it?), but lays no claim as to if or how that might be the case. A dark horse.

    The github repo dates to 2015 and so, it's not as long-in-the-tooth as Juice, but still, it likely leans on a more meager JavaScript standard than we have available today and quite possibly, like Juice resorts to parsing CSS code and interpreting it. It has about 1700 lines of Javascript and so is even larger than Juice! The last code contributions on github are early 2020 so at least it's being maintained which is good.

    Still, it also depends on cheerio, and so falls a little short of a native solution but worse, it does not provide us with any suggestion as to run-context (server side or client side).

    It's on npm, which is Node.js which suggests server-side JavaScript. It doesn't rule out that it works client-side, but there is zero indication provided that it does nor a test site, the way Juice provided. And like it or not, I associate npm primarily with Node.js and server side applications (rightly or wrongly).

    So for my needs, it goes respectfully into the too-hard basket. Failed, in a sense, by the poor quality of its own introductory presentation. An irony, because there is some nice documentation there, just not a nice introduction that spells out whether it runs client-side or not, how to if so, and how it's different from Juice and why we'd use it. All the obvious questions I have surfing in on it.

    css-inliner ๐Ÿ‘Ž

    Long story short, the introductory documentation fails this package even more than that for inline-css did. Again, it's on npm, and so looks targeted at server-side use and makes no effort to mention the other two (Juice or inline-css), or differentiate itself from them. The github repo dates back to 2015 as well and so it looks at some level to be an example of modern parallel development, this and inline-css emerging at the same time. And unsurprisingly, it again has around 1600 lines of JavaScript. The last code contribution was 2020 so again, at least it's being maintained which is good I guess.

    Still, no hint as to the run-context it supports (server-side and/or client-side) but hints, via its npm references and templating languages that it's a server-side tool not a client-side tool. Which doesn't rule out client-side application but again no claim that it works in that context, and no tips on how (if it does) and no demo site, so it's a respectful pass. Still seeking a lean native Javascript solution in preference to some pet project lacking clarity and exhibiting bloat.

    Native Javascript ๐Ÿ‘

    The failure to find an existing solution, leads me to (seeking) a native JavaScript implementation and the journey of discovery that lies behind that.

    document.styleSheets provides us with a collection of CSSStyleSheets and CSSStyleSheet.rules in turn provides all of the CSSStyleRules in use and Element.matches() tells us if CSSStyleRule.selectorText applies to a given element.

    window.getComputedStyle() provides rapid access to the complete set of computed styles. That is, crucially it has taken all those styles that position things relative to the browser window and calculated where, in real coordinates it landed. Among other things. Crucially, it also has resolved all of CSS variables. It describes what an element actually looks like on the screen, rather than in the abstract CSS.

    We can use the style sheets and the computed styles to update the style attribute of each element and then, when all is done the innerText and the innerHTML or outerHTML are available for the the text/plain and text/html MIME parts respectively.

    Given we're in-lining styles, and we don't want to actually change the element in the DOM (we're just aiming to copy it to the clipboard in one form or another), we have to take a copy of the DOM element and in-line the styles on that. We have to use the computed style from the source element however as it is rendered on screen and the copy is not (hence has not got computed styles). To wit, we will have a source and target element one that is in the DOM and provides computed styles, and one that is not in the DOM and receives in-lined style attributes.

    Importantly an implementation like this is maybe 200, or 300 lines of JavaScript and not 1500.

    That more or less covers us and we have a terse native JavaScript in-lining solution!

    But ... performance, performance ... turns out that it's not slow, but it's not fast either, let's take a look at performance next, before we dive into an actual code implementation of the above schema - next week's article.

  • I built a job board for the Space industry! link in comments
    2 projects | reddit.com/r/webdev | 9 Oct 2021
    - Web scraper: Cheerio and Puppeteer
  • What is the best language to use if I want to scan a webpage for certain keywords?
    1 project | reddit.com/r/AskProgramming | 22 Sep 2021
    I used https://cheerio.js.org/ in the past. It's awesome. You tell it what Dom elements to get. Can do all sorts of web scraping stuff. So easy to use too...
  • What is the best option to parse a RSS podcast feed (XML) with Nuxt.Js?
    2 projects | reddit.com/r/Nuxt | 21 Sep 2021
  • Web Scraping with Javascript and Node.js
    5 projects | dev.to | 1 Sep 2021
    Cheerio is a "fast, flexible & lean implementation of core jQuery." It lets us find nodes with selectors, get text or attributes, and many other things. We will pass the HTML to cheerio and then query it as we would in a browser environment.
  • How to Scrape Google SERPs Using WebScrapingAPI in Node.js
    2 projects | dev.to | 1 Sep 2021
    In the following section, we will use Node.js and some libraries like got and Cheerio to create the script that will get all the data from a SERP and format it nicely to be as understandable as possible.
  • Create An IMDB Web Scraper Using JS
    1 project | dev.to | 22 Aug 2021
    cheerio helps us to parse HTML in nodeJS. It's an affective and powerful technology used in webscraping in sever side implementation. The FS module should be pre-installed in the node_modules if you previously used npm init command.
  • XML Parsing Error
    1 project | reddit.com/r/GoogleAppsScript | 21 Aug 2021
    You may want to consider an alternative to XmlService, such as Cheerio or parsing the string itself.
  • How to scrape Bing Search with Node.js?
    2 projects | dev.to | 19 Aug 2021
    [ { position: 1, title: 'cheerio - js', link: 'https://cheerio.js.org/', displayed_link: 'https://cheerio.js.org', snippet: 'Cheerio parses markup and provides an API for traversing/manipulating the resulting data structure. It does not interpret the result as a web browser does. Specifically, it does not produce a visual rendering, apply CSS, load external resources, or execute JavaScript. This makes Cheerio โ€ฆ', sitelinks: { expanded: [Array] } }, { position: 2, title: 'GitHub - cheeriojs/cheerio: Fast, flexible, and lean ...', link: 'https://github.com/cheeriojs/cheerio', displayed_link: 'https://github.com/cheeriojs/cheerio', snippet: 'Jul 28, 2017 ยท Cheerio parses markup and provides an API for traversing/manipulating the resulting data structure. It does not interpret the result as a web browser does. Specifically, it does not produce a visual rendering, apply CSS, load external resources, or execute JavaScript. This makes Cheerio much, much faster than other solutions.' }, ...

What are some alternatives?

When comparing Electron and cheerio you can also consider the following projects:

jsdom - A JavaScript implementation of various web standards, for use with Node.js

puppeteer - Headless Chrome Node.js API

Faker.js - generate massive amounts of realistic fake data in Node.js and the browser

dotenv - Loads environment variables from .env for nodejs projects.

opencv - OpenCV Bindings for node.js

webworker-threads - Lightweight Web Worker API implementation with native threads

Prettyprint Object - Function to pretty-print an object with an ability to annotate every value.

react-native - A framework for building native applications using React

ssh2 - SSH2 client and server modules written in pure JavaScript for node.js

nodegit - Native Node bindings to Git.

electron-overlay-window - Creating overlays is easy like never before