nextauthjs / nextauthjs/next-auth
Conflicting peer dependency: @auth/core@0.2.5 with @auth/solid-start
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 28.4k
- Forks
- 4k
- PR merge metrics
- No merged PRs in 30d
Description
Environment
System:
OS: Windows 10 10.0.22621
CPU: (8) x64 Intel(R) Core(TM) i5-8365U CPU @ 1.60GHz
Memory: 1.63 GB / 7.82 GB
Binaries:
Node: 20.0.0 - C:\Program Files\nodejs\node.EXE
npm: 9.6.6 - C:\Program Files\nodejs\npm.CMD
Browsers:
Edge: Spartan (44.22621.1928.0), Chromium (114.0.1823.58)
Describe the issue
- "Conflicting peer dependency: @auth/core@0.2.5" with @auth/solid-start.
How to reproduce
simply npm init and run npm install @auth/solid-start@latest @auth/core@latest
Expected behavior
Well, I shouldn't need to use npm install --force but simply npm install
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the conflict with npm init and npm install @auth/solid-start@latest @auth/core@latest, using the versions and environment described in the issue. Inspect the dependency metadata for @auth/solid-start and @auth/core; done means a normal npm install succeeds without --force and the peer-dependency warning is gone.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nodejs
- Domain
- authentication
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100