solid-primitives VS linkedom

Solid.js is already pretty powerful, but even so, there are things it cannot do out of the box. Here's where the community comes in and provides packages to enhance your development experience: solid-primitives.

As for component libraries, I also just don't like or use them anymore. I find that they just get in my way. What I really like is the community primitive packages that solve all the lower level challenges when building certain types of components. I personally find that to be enough.

Check out Solid primitives.

This might be helpful: https://github.com/solidjs-community/solid-primitives/tree/main/packages/event-bus

So you can have a look at the test in the solid-primitives repository.

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