Because package.el lacks a mechanism for specifying any constraints on dependency versions (apart from a minimum version) this means that any package depending on nvm will pick up the latest version of dash-functional and therefore print this warning. This breaks, for example, my package's CI.
This PR solves the problem by upgrading dash and dropping the dash-functional dependency.
The Dash folks have recently decided to merge
dash-functional
intodash
. The latest version ofdash-functional
now emits a byte-code compilation warning when it is loaded.Because
package.el
lacks a mechanism for specifying any constraints on dependency versions (apart from a minimum version) this means that any package depending onnvm
will pick up the latest version ofdash-functional
and therefore print this warning. This breaks, for example, my package's CI.This PR solves the problem by upgrading
dash
and dropping thedash-functional
dependency.