payloadcms / payload

Payload is the open-source, fullstack Next.js framework, giving you instant backend superpowers. Get a full TypeScript backend and admin panel instantly. Use Payload as a headless CMS or for building powerful applications.
https://payloadcms.com
MIT License
23.58k stars 1.5k forks source link

Error: Mismatching "payload" dependency versions found: @payloadcms/ui/shared@3.0.0-beta.94 (Please change this to 3.0.0-beta.95). #7955

Closed zelenovsky closed 1 month ago

zelenovsky commented 1 month ago

Link to reproduction

No response

Environment Info

Binaries:
  Node: 20.11.0
  npm: 10.2.4
  Yarn: N/A
  pnpm: 9.5.0
Relevant Packages:
  payload: 3.0.0-beta.95
  next: 15.0.0-canary.104
  @payloadcms/db-postgres: 3.0.0-beta.95
  @payloadcms/graphql: 3.0.0-beta.95
  @payloadcms/next/utilities: 3.0.0-beta.95
  @payloadcms/richtext-lexical: 3.0.0-beta.95
  @payloadcms/translations: 3.0.0-beta.95
  @payloadcms/ui/shared: 3.0.0-beta.95
  react: 19.0.0-rc-06d0b89e-20240801
  react-dom: 19.0.0-rc-06d0b89e-20240801
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.6.0: Mon Jul 29 21:13:04 PDT 2024; root:xnu-10063.141.2~1/RELEASE_ARM64_T6020
  Available memory (MB): 16384
  Available CPU cores: 12

Describe the Bug

I am getting this error: Error: Mismatching "payload" dependency versions found: @payloadcms/ui/shared@3.0.0-beta.94 (Please change this to 3.0.0-beta.95). but I have 95 version of ui package

Reproduction Steps

  1. pnpm update
  2. pnpm dev (the same issue with pnpm devsafe)

Adapters and Plugins

No response

tylandavis commented 1 month ago

I would suggest you try removing your node_modules directory and pnpm.lock file, and then try reinstalling packages. Perhaps there is something being cached with pnpm.

Wiz1991 commented 1 month ago

Check that you don't have a payload dep set to be ^3.0.0.beta-94. Remove the ^

zelenovsky commented 1 month ago

@tylandavis thanks, removing node_modules solved the issue

github-actions[bot] commented 3 weeks ago

This issue has been automatically locked. Please open a new issue if this issue persists with any additional detail.