You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thank you for the effort in this library – I am testing happy-dom to see if I can achieve some performance improvement over jsdom. Our case is more of a server-side rendering: we have a browser library that manipulates the existing DOM very very heavily (mutation observers, tree walkers, attribute modifications, node additions/removals etc). JSDom spends a lot of time in various places.
While testing happy-dom, I am encountering several things, I will be submitting them as issues here as I see them. Here is the first one.
It looks like progress is on-going in that PR, but it's a pretty big change. I could put together a PR that just replaces URL.ts with node's built-in "url" module.
Hi there!
Thank you for the effort in this library – I am testing happy-dom to see if I can achieve some performance improvement over jsdom. Our case is more of a server-side rendering: we have a browser library that manipulates the existing DOM very very heavily (mutation observers, tree walkers, attribute modifications, node additions/removals etc). JSDom spends a lot of time in various places.
While testing happy-dom, I am encountering several things, I will be submitting them as issues here as I see them. Here is the first one.
URL
object does not have asearchParams
property, onlysearch
: https://developer.mozilla.org/en-US/docs/Web/API/URL/searchParamsThe text was updated successfully, but these errors were encountered: