new unsatisfied peer dependencies with latest verion

i’ve been receiving renovate PRs for the new v7 in some of my projects now that you’ve promoted it to latest. i had upgraded a few of my projects to the prerelease of v7 already without issue.

however, i’m now seeing some new failures due to unsatisfied peer dependencies with the new version. you can see an example of this in this build output. i use npm ls to ensure that peer dependencies are compatible (it will exit non-zero if there is a conflict).

the projects that i’m seeing these issues in are not react projects, so i have no reason to depend on the peer packages other than because of the use of cucumber, so i would prefer not to depend on them directly. could you please satisfy these peer dependencies on your end by making them prod dependencies of cucumber?

[davidjgoss]

Hey @ericlanteigne-quest - the fix is done and this should be released soon.

[davidjgoss]

Thanks for raising @travi

These React-related dependencies come via our HTML formatter and some React libraries it uses.

peer dep missing: react@^16.3.2, required by react-accessible-accordion@3.3.3
peer dep missing: react-dom@^16.3.3, required by react-accessible-accordion@3.3.3

There’s already a PR merged to allow React 17 for react-accessible-accordion here https://github.com/springload/react-accessible-accordion/pull/307 so hopefully that’ll get released shortly and we can bring that in.

peer dep missing: @types/react@>=16, required by react-markdown@5.0.3

I’ll raise it with that project. I don’t think it should require consuming projects to install types for react.