Actually, maybe this is pressing my luck, but ... if that's a hack, and it's not something that's appropriate to petition to be changed in cypress, then I'm still stuck. Another thing I tried was locally modifying

node_modules/@vue/cli-plugin-e2e-cypress/index.js

to no longer make that call to `@vue/cli-shared-utils`'s

modules

package in order to determine the location of the

cypress

executable. Instead, just use

#{__dirname}/../../cypress/bin/cypress

. Is there something horribly wrong with this? It does work, but if it did not bring problems with it I would've expected this implementation to begin with, rather than the complex

require

-based approach in

@vue/cli-shared-utils/lib/module.js

, which seems to expect that the binary be in the

exports

section of cypress 10's

package.json

. What's the right way to go about trying to achieve cypress 10 compatibility with

@vue/cli-plugin-e2e-cypress

given the nature of this issue?