https://cypress.io logo
So, on a lark, locally in `node_modules/cypress/pa...
# e2e-testing
o
So, on a lark, locally in
node_modules/cypress/package.json
I added this code:
Copy code
... "exports": { ...
     "./bin/cypress": {
      "import": "./bin/cypress",
      "require": "./bin/cypress"
    },
    ...
  }
. Now, I have no idea what that actually does in terms of what the
exports
section is intended for. But it does restore compatibility of cypress 10 with
@vue/cli-plugin-e2e-cypress
. My question is: is this an illegitimate hack? Should the binary executable not actually be placed in the exports section of package.json, despite that this fixes that plugin? Or is it something that's acceptable to do, and
@vue/cli-shared-utils
is actually correct in expecting that export before determining that executable `bin/cypress`'s location?