chore: use resolve-package-path to resolve installed dependency versions more reliably

[astone123]

• Closes Launchpad CT onboarding dependencies screen not always reliable #25782

Additional details

There are some dependencies that we can't resolve with require.resolve, because of one of the following reasons:

• The package has exports defined, but package.json is not one of the exports
• Some packages don't have entrypoints (like in the case of react-scripts, there is no entrypoint, just a bin).

We need to find a way around these limitations so that we can figure out if a dependency is installed, and if it is, which version is installed. Lachlan and I found a package called resolve-package-path that does the trick, working around the exports and entrypoint limitations and allowing us to detect dependencies that are installed.

TLDR: It looks like we can't use require.resolve to figure out which dependencies of which packages are installed.

Further reading

Steps to test

1. yarn create vite my-app --template react
2. Install dependencies in my-app
3. cd into node_modules/react, remove package.json from the exports key in package.json
4. Open Launchpad with my-app and click Component Testing
5. Verify that the framework and bundler (React and Vite) are automatically detected and are selected in the dropdowns

How has the user experience changed?

There should be no noticeable change for the user

PR Tasks

• Have tests been added/updated?
• [na] Has a PR for user-facing changes been opened in cypress-documentation?
• [na] Have API changes been updated in the type definitions?

[cypress]

3 flaky tests on run #44605 ↗︎

0

5116

74

0

3

Details:

Merge branch 'launchpad-dep-resolution-exports' of github.com:cypress-io/cypress...
Project: cypress	Commit: 59f89ca2be
Status: Passed	Duration: 14:02 💡
Started: Mar 8, 2023 4:23 PM	Ended: Mar 8, 2023 4:37 PM

  cypress/e2e/cypress/cypress.cy.js • 3 flaky tests • 5x-driver-electron

View Output Video

Test		Artifacts
... > correctly returns currentRetry		Output Video
... > correctly returns currentRetry		Output Video
... > correctly returns currentRetry		Output Video

_{This comment has been generated by cypress-bot as a result of this project's GitHub integration settings.}

[mike-plummer]

@astone123 Still seeing a lot of test failures here, happy to ✅ once those are resolved

[astone123]

@mike-plummer okay we should be good now