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
npm ls can-validate-validatejs gives me (for CanJS 5.33.2 - but this will be no different for later versions, as 1.1.1 is the latest for the can-define-validate-validatejs package):
i.e. can-define-validate-validatejs is using a version range that is not compatible with the top-level can package and is leading to a duplicated local copy of the older dependency. This is in fact complicating a local workaround for another issue reported on can-validate-validatejs, freshly reported: canjs/can-validate-validatejs#44
I now have to concoct a build-step workaround which somehow swaps out both packages with fixed versions.
The text was updated successfully, but these errors were encountered:
Literally the only line difference for can-validate-validatejs sofar (with aforementioned issue untreated) appears to be a "use strict" directive. Can you please just bump the dependency from the 0.1.x range into the 1.0.x range and publish a 1.1.2 version of the can-define-validate-validatejs package?
That should still fit version constraints, even for the 5.x range of the main can package.
npm ls can-validate-validatejs
gives me (for CanJS 5.33.2 - but this will be no different for later versions, as 1.1.1 is the latest for thecan-define-validate-validatejs
package):i.e.
can-define-validate-validatejs
is using a version range that is not compatible with the top-levelcan
package and is leading to a duplicated local copy of the older dependency. This is in fact complicating a local workaround for another issue reported oncan-validate-validatejs
, freshly reported: canjs/can-validate-validatejs#44I now have to concoct a build-step workaround which somehow swaps out both packages with fixed versions.
The text was updated successfully, but these errors were encountered: