You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's fairly well-established that having multiple versions of this package installed in a repo can cause problems, and I see that for the 8.2.0 alpha @storybook/test was updated to use 10.1.0, removing the semver range that was allowed previously.
I'm wondering if it would be possible to go back to allowing a semver range, which should make it more likely that package managers can dedupe @testing-library/dom (at least within a given major version). Alternatively, maybe @testing-library/dom could be made a peer dependency, similar to what was recently done in @testing-library/react?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
It's fairly well-established that having multiple versions of this package installed in a repo can cause problems, and I see that for the 8.2.0 alpha
@storybook/test
was updated to use 10.1.0, removing the semver range that was allowed previously.I'm wondering if it would be possible to go back to allowing a semver range, which should make it more likely that package managers can dedupe
@testing-library/dom
(at least within a given major version). Alternatively, maybe@testing-library/dom
could be made a peer dependency, similar to what was recently done in@testing-library/react
?Thanks!
Beta Was this translation helpful? Give feedback.
All reactions