I'm using this package to help do a very large migration and I noticed that the only function being used is isDate from date-fns. However, we are actually looking at using date-fns 1.x and 2.x side-by-side using package aliasing to help do a granular migration but the problem is that this package will bring in date-fns 2.x even though there's no difference between behavior for isDate from v1 / v2, and there's an extra date-fns brought into the node_modules tree.
I'd have to dig into whether this impacts bundle size inadvertently but I don't see too much of an issue using a wildcard version if only depending on isDate.
Changes
Use * dependency versioning to support date-fns 1.x and 2.x during a migration scenario
I'm using this package to help do a very large migration and I noticed that the only function being used is
isDatefromdate-fns. However, we are actually looking at using date-fns 1.x and 2.x side-by-side using package aliasing to help do a granular migration but the problem is that this package will bring in date-fns 2.x even though there's no difference between behavior forisDatefrom v1 / v2, and there's an extradate-fnsbrought into the node_modules tree.I'd have to dig into whether this impacts bundle size inadvertently but I don't see too much of an issue using a wildcard version if only depending on
isDate.Changes
*dependency versioning to supportdate-fns1.x and 2.x during a migration scenariotypesfor good measure