Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dependency Conflict: next-navigation-guard Incompatible with [email protected] #22

Open
bs-vinay-parmar opened this issue Jan 24, 2025 · 1 comment

Comments

@bs-vinay-parmar
Copy link

Description:
I encountered a dependency resolution issue while trying to install next-navigation-guard in my project, which uses [email protected]. The error message indicates that next-navigation-guard requires next versions ^14 || ^15, leading to a conflict.

Error Log:

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/next
npm ERR! next@"13.2.4" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer next@"^14 || ^15" from [email protected]
npm ERR! node_modules/next-navigation-guard
npm ERR! next-navigation-guard@"*" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! For a full report see:
npm ERR! /home/bs/.npm/_logs/2025-01-23T13_12_03_700Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /home/bs/.npm/_logs/2025-01-23T13_12_03_700Z-debug-0.log

Steps to Reproduce:

  1. Create a new project with [email protected].
  2. Run npm install next-navigation-guard.

Suggested Resolution:
Consider updating the peerDependencies of next-navigation-guard to support [email protected] versions, or provide guidance on the recommended next steps.

Additional Information:
I am aware of the workaround to use --force, but I prefer not to use this due to potential issues with prod deployment. Any insights or recommendations on how to resolve this issue would be greatly appreciated. Thank you!

@wherehows
Copy link

me tooooo T_T

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants