-
-
Notifications
You must be signed in to change notification settings - Fork 755
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
devDependency for jsdom is very outdated #461
Comments
Heya, thanks for filing this. I am unsure if we have the time to address this anytime soon. cc @tdeekens |
I don't know that much purify but if I can be of any help don't hesitate to guide me :) |
Thanks for the offer :) The problem is, that we would have to renovate the test suite to make sure it is compatible with later versions of jsdom. I am personally not involved with anything jsdom (a.k.a. have no clue where to get started in this case) and primarily take care of the core library. If you have any ideas where to start patching, I'd be super happy to look into that together. |
Closing this for now |
I just update test and they are all passing now with new jsdom version. |
DOMPurify uses jsdom version 8.x.x as a devDependency, however jsdom is currently only supporting version 16 and above.
See https://raw.githubusercontent.com/jsdom/jsdom/master/.github/ISSUE_TEMPLATE.md
Background & Context
There some bugs in older version of jsdom, that can crash purify execution.
Test Case
Very simple domPurify test case to trigger the exception:
Bug
This issue #375 is closed because it's a bug in jsdom, but as purify is not up to date the bug is still present in purify.
Input
Given output
This request have been already asked here #449 but it didn't point that an existing bug exist and require this upgrade. I understand that it has a big impact on test but it's make purify unusable as any text like that will not be parsable by purify and will failed.
The text was updated successfully, but these errors were encountered: