We don't have package-lock.json and the dependencies are specified with a hat ^, so this means the ranges are pretty loose.
Tests are failing in main, and I realized that's because they are installing chloride@2.3.0, because we specified the range "chloride": "^2.2.8".
This PR uses tilde instead of hat, to make the version range more narrow, and thus rejecting chloride@2.3.0, but sticking with chloride@2.2.x. The tests now pass. We should try to support chloride@2.3.0 too, but that's another issue.
We don't have package-lock.json and the
dependencies
are specified with a hat^
, so this means the ranges are pretty loose.Tests are failing in
main
, and I realized that's because they are installingchloride@2.3.0
, because we specified the range"chloride": "^2.2.8"
.This PR uses tilde instead of hat, to make the version range more narrow, and thus rejecting
chloride@2.3.0
, but sticking withchloride@2.2.x
. The tests now pass. We should try to supportchloride@2.3.0
too, but that's another issue.