-
-
Notifications
You must be signed in to change notification settings - Fork 754
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consider supporting happy-dom #876
Comments
Oh, nice - I did not have that on my radar :D
We are open to that.
That would be great! We would likely need the testsuite to be extended and update the Github actions, etc. - and maybe the existing tests already help identifying possible sanitizer bypasses in Happy DOM they might want to address. What would you say are next steps? |
Thinking I should open a PR that at least has the adjusted tests set up so that it's easy to review and discuss specific test failures - that way once we identify specific scenarios that fail, we can build up a list of items that need to be resolved |
That sounds most excellent :D Thank you. Please do let know if any help is needed. |
I am wondering, is happy-dom still maintained? No movement for two months it seems... |
It was very active until 2 months ago. It appears the author is a single maintainer (which I didn't realize before) and has not been active, perhaps something has prevented them from being available recently. |
Aye, okay, no worries - I was just surprised when checking the repo 😅 |
Closing this for now, it seems that the ball is in happy-dom's corner and the project is inactive. Please reopen if anything changes. |
This can be re-opened, |
Ooooh, nice! cc @luxaritas |
I've recently been using happy-dom with vitest instead of jsdom due to its focus on performance. It would be awesome if DOMPurify could also support happy-dom in NodeJS. Since this doesn't appear to have been brought up before, I'm curious if this would be of interest to the project, though I understand if there are scope/maintenance concerns.
I did some very basic checks with happy-dom on the current test suite, and while I get the impression the number of unique errors is fairly limited, it unfortunately doesn't seem completely trivial either. I would be happy to provide some assistance if it is of interest, though would probably need some guidance being a new contributor.
The text was updated successfully, but these errors were encountered: