happy-dom VS linkedom

Next we’ll install Vitest and happy-dom to the project by running:

JSDOM and happy-dom for DOM and browser API mocking

https://github.com/capricorn86/happy-dom/issues/618. Looks like some work was merged recently.

I think you mean jsdom. You can try Happy DOM

Well, I've actually done it using axios + happy-dom.

You may have heard of vite, the slim fast dev server that scored an amazing as deserved 98% satisfaction on the state of js survey 2021. It's creators found unit testing too cumbersome and slow and decided to add their own perspective to the task. The result is vitest: it runs a vite server under the hood to transform the code to test as fast as possible, uses an enhanced flavor of chai to have jest-compatible assertions, integrates DOM mocking using jsdom or happy-dom and even the tiny-spy library that was just built as a separate library to allow for easy reuse is small and compatible with jest.

happy-dom, more lightweight

linkedom is your answer

linkedom - to parse HTML into a workable DOM. I used to use jsdom, but I switch for performance reasons.

For simple scraping where the content is fairly static, or when performance is critical, I will use linkedom to process pages.

https://github.com/WebReflection/linkedom

When the content is complex or involves clicking, Playwright is probably the best tool for the job.

https://github.com/microsoft/playwright

I recently started using linkedom for this and it has been an absolute joy

This looks great. I wonder how it compares to linkedom (repo[1], writeup[2]), which I have found to be fantastic.

[1]: https://github.com/WebReflection/linkedom

[2]: https://webreflection.medium.com/linkedom-a-jsdom-alternativ...

linkedom, fastest, but lacks essential features

Other things to do would be to use linkedom instead of JSDom, look into a better assertion library than assert etc.

Sounds somewhat similar to linkedom[1], which performs nicely.

[1]: https://github.com/WebReflection/linkedom