Skip to content

Missing peer dependency in react-scripts #8022

Closed

Description

@Andarist

You have peerDependenciesMeta there without actual peerDependencies - I believe this doesn't work as expected, peerDependenciesMeta requires peerDependencies to be there as it's merely additional information, not a replacement.

Activity

  1. ianschmitz commented on Nov 24, 2019

    @ianschmitz
    Contributor

    Hmm it would seem you're correct: https://github.com/yarnpkg/yarn/pull/6671/files.

    Adding under peerDependencies will start throwing warnings for folks that don't have npm@6.11.0 or later.

    We may want to do this as part of our v4 release. I'll mark as such and see what the other maintainers think.

  2. added this to the 4.0 milestone on Nov 24, 2019
  3. Andarist commented on Nov 24, 2019

    @Andarist
    ContributorAuthor

    From what I understand CRA+TS would be broken for strict package managers like pnpm or yarn in pnp mode without this peer dependency specified. I was facing similar problem lately for the other package and we decided to just go with specifying peer dep and marking it as optional. We can always recommend using new version of npm and on older versions it will merely cause a warning - things will still be very much functional, so... 🤷‍♂

  4. ianschmitz commented on Nov 24, 2019

    @ianschmitz
    Contributor

    Good point. Oct 21 appears to have been the first Node release that included npm >= 6.11. I'm okay with the warning to support the other package managers.

  5. modified the milestones: 4.0, 3.4, 3.3 on Nov 24, 2019
  6. locked and limited conversation to collaborators on Dec 3, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions