-
Notifications
You must be signed in to change notification settings - Fork 1.1k
USWDS - Hotfix: Remove classlist-polyfill dependency #6012
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
Conversation
amyleadem
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me. I was able to successfully complete the following:
- Run
npm install - Run
npm start
Components as expected in Chrome, Safari, and Firefox.
|
Oh, one small note: It might be good to add a note to the "Breaking change" section of the PR description that this will remove some IE11 support. Just think it would be good to be super clear in case there are projects that still support IE? |
|
While this dependency has a potential DoS vulnerability via regex, we don't consider it exploitable from the front end of applications. Even so, it make sense to remove this dependency. |
Updated USWDS to v3.8.2 - [new release](https://github.com/uswds/uswds/releases/tag/v3.8.2) - [Removed the `classlist-polyfill` dependency in issue 6012](uswds/uswds#6012)
Summary
Removed the IE11
classlist-polyfilldependency that caused a DoS VulnerabilityBreaking change
This is a potentially breaking change.
This polyfill added support for the classList property in IE11, which now has partial support.
Related issue
Closes #6008
Related pull requests
The remaining IE11 polyfills are removed in #4692
Preview link
Storybook preview →
Problem statement
The
classlist-polyfilldependency was causing a DoS vulnerability affecting downstream projects.Solution
Remove the polyfill now that IE11 is no longer officially supported.
Testing and review
npm installand confirm there are no issuesnpm run startand confirm there are no build errorsDependency updates
1.2.0