Conflicting peer dependency: @auth/core@0.2.5 with @auth/solid-start

rattleSSnake commented 1 year ago

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

aronmal commented 11 months ago

Can the dependencies please be updated? I also get these warnings every time:

 WARN  Issues with peer dependencies found
.
└─┬ @auth/solid-start 0.1.1
  ├── ✕ unmet peer @auth/core@"~0.2.2 || ^0.2.2": found 0.12.0
  └── ✕ unmet peer solid-start@^0.2.14: found 0.3.5

rattleSSnake commented 11 months ago

@aronmal use solid-start-oauth it's better

aronmal commented 11 months ago

Good to know, but I also use oauth and credentials. Otherwise I would replace @auth with DIY, but I have other concerns at the moment.

I now also added pnpm overrides to have the warnings gone.

nextauthjs / next-auth