<!-- Vote on feature requests by adding a 👍. This helps maintainers prioritize what to work on. * Please fill out this template with all the relevant information so we can understand what's going on and fix the issue. We appreciate bugs filed and PRs submitted! * Please make sure that you are familiar with and follow the Code of Conduct for this project (found in the CODE_OF_CONDUCT.md file). It'd be great if after the discussion you're the one who submits the PR that implements this feature. If you've never done that before, that's great! Check this free short video tutorial to learn how: http://kcd.im/pull-request --> ### Describe the feature you'd like: - remove `jest-environment-jsdom-sixteen` package in devDependencies which isn't used - https://github.com/SimenB/jest-environment-jsdom-sixteen -  <!-- A clear and concise description of what you want to happen. Add any considered drawbacks. Note: if you're proposing a new custom matcher, please keep in mind jest-dom's guiding principles as stated here https://github.com/testing-library/jest-dom#guiding-principles In particular, keep this in mind: > the overall criteria for what is considered a useful custom matcher to add to > this library, is that doing the equivalent assertion on our own makes the test > code more verbose, less clear in its intent, and/or harder to read. --> ### Suggested implementation: <!-- Helpful but optional 😀 --> - remove the package from package.json ### Describe alternatives you've considered: <!-- A clear and concise description of any alternative solutions or features you've considered. --> - N/A ### Teachability, Documentation, Adoption, Migration Strategy: <!-- If you can, explain how users will be able to use this and possibly write out a version of the docs. --> - since it's not used, it shouldn't change anything