Skip to content

Peer Dependency Conflict and Deprecation Warnings During npm Install #3

@devavikalabs

Description

@devavikalabs

Description:
When running npm install, several peer dependency conflicts and deprecation warnings were encountered. The main issue appears to be related to React version mismatches and outdated dependencies in the package tree.

Steps to Reproduce:

  1. Run npm install in the project directory.
  2. Observe the warnings and errors related to peer dependency conflicts and deprecated packages.

Expected Behavior:

  • Dependencies should resolve correctly without overriding peer dependencies.
  • No critical warnings or deprecation messages should appear.

Actual Behavior:

  • Multiple peer dependency conflicts related to react@19.0.0 and dependencies expecting react@16.x, 17.x, or 18.x.
  • Several deprecated packages detected, including:
    • inflight@1.0.6 (memory leak warning)
    • npmlog@5.0.1 (no longer supported)
    • rimraf@3.0.2 (prior versions not supported)
    • glob@7.2.3 (prior versions not supported)
    • are-we-there-yet@2.0.0 (no longer supported)
    • gauge@3.0.2 (no longer supported)
    • @humanwhocodes/config-array@0.11.14 (suggests @eslint/config-array instead)
    • @humanwhocodes/object-schema@2.0.3 (suggests @eslint/object-schema instead)

Error Log:

npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: lucide-react@0.378.0
npm WARN Found: react@19.0.0
npm WARN node_modules/react
npm WARN   react@"^19.0.0" from the root project
npm WARN   75 more (@floating-ui/react-dom, @radix-ui/react-accordion, ...)

npm WARN Could not resolve dependency:
npm WARN peer react@"^16.5.1 || ^17.0.0 || ^18.0.0" from lucide-react@0.378.0
npm WARN node_modules/@stackframe/stack-ui/node_modules/lucide-react
npm WARN   lucide-react@"^0.378.0" from @stackframe/stack-ui@2.5.37
npm WARN   node_modules/@stackframe/stack-ui
...

Vulnerabilities Reported:

7 vulnerabilities found (2 low, 3 moderate, 1 high, 1 critical)
To address issues that do not require attention, run:
  npm audit fix
To address all issues (including breaking changes), run:
  npm audit fix --force
Run `npm audit` for details.

Environment:

  • Node.js version: v20.18.0
  • npm version: 11.0.0
  • Operating System: windows 11

Screenshots:

Image

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions