← All tasks
javascripttesting-library/jest-dom #608Not a task: not reproduced

Is it possible to have a version not depending on jest, @jest/globals ?

envgap__testing-library__jest-dom-608

01 / FAILURE SIGNATURE

As reported upstream

No identifying execution failure has been captured.
Not a benchmark task.
  • In a clean container the reported failure did not reproduce, or the known fix did not make the project run.

02 / ENVIRONMENT RECIPE

Base commit
78a2934e3bcdd2140bd8e814a5050c7c37c4d112
Manifest
package.json
Reproduce
Awaiting issue-specific recipe
Run under trace
Awaiting a meaningful runtime command

03 / ORIGINAL ISSUE TEXT

testing-library/jest-dom #608 · read the original issue
<!--



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:



<!--

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.

-->

A version of this package that does not have jest / @jest/globals as peer dependencies. These dependencies are installed automatically by npm (in recent versions) and if you're using Vitest and not Jest, you still end up installing tons of jest-related dependencies.



Any advice on how this could get implemented? I'm willing to help btw :)



### Suggested implementation:



<!-- Helpful but optional 😀 -->



### Describe alternatives you've considered:



<!--

A clear and concise description of any alternative solutions or features you've

considered.

-->



### 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.

-->

Continue on GitHub ↗

04 / LABELS

Labels from the report text only; not yet run

No supported category has been assigned.

Label rules and the text that matched
[]