If you specify a version constraint when running a package executable, dpx will first check to see if you have a version of that package already globally activated that satisfies that version constraint:
dpx dependency_validator@^4.0.0
This makes the process faster by avoiding unnecessary network requests.
But, if you're omitting the version constraint for brevity, like this:
dpx dependency_validator
Then any version of that package, if already activated, will technically satisfy the omitted version constraint. That may be fine, but it may lead to confusing behavior if you were expecting to be able to use an option or some behavior that was only recently released.
Would a better default be to always try to install the latest version of a package if no version constraint is specified?
If you specify a version constraint when running a package executable, dpx will first check to see if you have a version of that package already globally activated that satisfies that version constraint:
This makes the process faster by avoiding unnecessary network requests.
But, if you're omitting the version constraint for brevity, like this:
Then any version of that package, if already activated, will technically satisfy the omitted version constraint. That may be fine, but it may lead to confusing behavior if you were expecting to be able to use an option or some behavior that was only recently released.
Would a better default be to always try to install the latest version of a package if no version constraint is specified?