Replies: 2 comments 6 replies
-
It is not true, see here: https://www.npmjs.com/package/@next-auth/typeorm-legacy-adapter/v/0.0.2-canary.129 If I had to guess, you use Yarn PnP, which notoriously behaves strangely: #1034, #1306, vercel/next.js#20955 Although we COULD update internally to |
Beta Was this translation helpful? Give feedback.
6 replies
-
For further investigation, we will need a reproduction |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Description 🐜
dependencies:
in package.json from Version 3.28.0 are not published on npm.
Same applies for previous released versions. They are dependent on not existing versions from the same package.
Thanks for looking into it.
Is this a bug in your own project?
No
How to reproduce ☕️
npm i -S next-auth
Screenshots / Logs 📽
npm i -S next-auth
npm ERR! code ETARGET
npm ERR! notarget No matching version found for @next-auth/[email protected].
npm ERR! notarget In most cases you or one of your dependencies are requesting
npm ERR! notarget a package version that doesn't exist.
npm ERR! notarget
npm ERR! notarget It was specified as a dependency of 'next-auth'
Environment 🖥
System:
OS: Linux 4.19 Ubuntu 20.04.2 LTS (Focal Fossa)
CPU: (12) x64 Intel(R) Core(TM) i7-8850H CPU @ 2.60GHz
Memory: 11.72 GB / 12.32 GB
Container: Yes
Shell: 5.0.17 - /usr/bin/bash
Binaries:
Node: 14.17.4 - ~/.nvm/versions/node/v14.17.4/bin/node
npm: 6.14.14 - ~/.nvm/versions/node/v14.17.4/bin/npm
npmPackages:
next: 11.1.0 => 11.1.0
react: 17.0.2 => 17.0.2
Contributing 🙌🏽
No, I am afraid I cannot help regarding this
Beta Was this translation helpful? Give feedback.
All reactions