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
Our packages, especially the legacy ones, have a number of peer dependencies specified with a wide range, e.g. ^4.4.0 || ^5.0.0. Generally, we're keeping our dev dependencies at the upper bound (e.g. 5.5) and have no real way of knowing that the packages actually build against the lower bound (e.g. 4.0).
At the very least we should make sure our packages build. Running the tests would be great, but I'm worried it would complicate the tests too much, as the results would likely be different based on the dependency versions that we use.
The text was updated successfully, but these errors were encountered:
Our packages, especially the legacy ones, have a number of peer dependencies specified with a wide range, e.g.
^4.4.0 || ^5.0.0
. Generally, we're keeping our dev dependencies at the upper bound (e.g.5.5
) and have no real way of knowing that the packages actually build against the lower bound (e.g.4.0
).At the very least we should make sure our packages build. Running the tests would be great, but I'm worried it would complicate the tests too much, as the results would likely be different based on the dependency versions that we use.
The text was updated successfully, but these errors were encountered: