app VS jsdom

nickytonline posted on Mar 13, 2024

fix: now workspace settings and new page have a fixed footer for CTAs #2982

View on GitHub

chore: removed prettier intergrations from eslint #2635

fix: add missing skeleton loader for insights panel #2524

With these questions, I decided to do my experiments based on two projects that I am involved with: the first is OpenSauced, and the second is okuyun.org.

At OpenSauced, we're using Next.js to build out the main application.

feat: add most used languages graph #2158

feat: Svelte added to interests dropdown list #2168

We believe in making the OpenSauced experience great for everyone who uses it and all our contributors. We welcome continued contributions, including issues, bug reports, pull requests, blog posts written about your OpenSauced experience, and your feedback. If you want to learn more about how to use OpenSauced to see how your projects are doing, check out our Introduction to OpenSauced or get started today.

If you happen to be using React Testing Library in your project, you'll need to keep the jsdom dev dependency installed.

Readability.js requires a DOM object to parse the readable content from a website. That's why we create a DOM object with JSDOM and provide the HTML from the page and its current URL. By the way, the browser may have had to follow HTTP redirects, so the current URL doesn't necessarily have to be the one we provided initially. The parse function of the library returns the following result:

This was the basic usage of JSDOM. If you want to learn more, please check out this documentation.

Web scraping, while immensely useful, often requires developers to navigate a sea of tools and libraries, each with its own quirks and intricacies. Whether it's JSDOM, Cheerio, Playwright, or even just plain old vanilla JS in the DevTools console, moving between these platforms can be a challenge.

React testing library uses jsdom (or others like happy-dom) under the hood to emulate the browser environment and enable testing of different properties. but it doesn't render the component in an actual browser meaning the styles can't be computed and the returned computed style is just an object with the correct keys but empty strings as values.

Note: In order to use the library jsdom to scrape the HTML response we need to avoid the @import statements in the CSS.

The code uses jSDom to render the app but I was wondering if it's possible to run the app without the UI to be able to use a library like that to generate the string from react element.

JSDOM as the DOM environment for running our tests