Error: cannot connect to Postgres. Details: Cannot read properties of undefined (reading 'setTypeParser')

[yayashn]

Link to reproduction

No response

Environment Info

> payload-catalyst@1.0.0 payload /Users/y/Desktop/payload-catalyst
> cross-env NODE_OPTIONS=--no-deprecation payload "info"


Binaries:
  Node: 20.12.1
  npm: 10.5.0
  Yarn: N/A
  pnpm: 8.14.2
Relevant Packages:
  payload: 3.0.0-beta.96
  next: 15.0.0-canary.104
  @payloadcms/email-nodemailer: 3.0.0-beta.96
  @payloadcms/graphql: 3.0.0-beta.96
  @payloadcms/next/utilities: 3.0.0-beta.96
  @payloadcms/plugin-cloud: 3.0.0-beta.96
  @payloadcms/richtext-lexical: 3.0.0-beta.96
  @payloadcms/translations: 3.0.0-beta.96
  @payloadcms/ui/shared: 3.0.0-beta.96
  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.1.0: Mon Oct  9 21:32:11 PDT 2023; root:xnu-10002.41.9~7/RELEASE_ARM64_T6030
  Available memory (MB): 36864
  Available CPU cores: 12

Describe the Bug

Get this error upon starting a blank project with vercel postgres:

[23:37:03] ERROR: Error: cannot connect to Postgres. Details: Cannot read properties of undefined (reading 'setTypeParser')

Reproduction Steps

-> pnpm create-payload-app@beta
-> Choose blank project
-> Enter vercel postgres database uri
-> pnpm dev

Also I think the .env doesn't automatically update with the url given to the CLI tool - though the issue persists even when I manually update the env variable.

Adapters and Plugins

db-vercel-postgres

[gjohnsx]

i'm also getting this error.

i chose vercel postgres with npx create-payload-app@beta but then in vercel storage i chose the supabase integration lol. not sure if that matters but the supabase connector is new in vercel postgres.

[xfloor]

i'm getting the same error, looks like something wrong with db-vercel-postgres adapter.
postgres with local db works fine.

[calebfoster]

try manually adding pg to your package file. seems like there's an issue when trying to import types from pg library.

yarn add pg

[yayashn]

try manually adding pg to your package file. seems like there's an issue when trying to import types from pg library.

yarn add pg

This removes the error but now I get stuck on Pulling schema from database.... This is probably for another issue though

 ⨯ ErrorEvent {
  digest: '3527995339',
  [Symbol(kTarget)]: WebSocket {
    _events: [Object: null prototype] {
      error: [Function],
      message: [Function],
      close: [Function],
      open: [Function]
    },
    _eventsCount: 4,
    _maxListeners: undefined,
    _binaryType: 'arraybuffer',
    _closeCode: 1006,
    _closeFrameReceived: false,
    _closeFrameSent: false,
    _closeMessage: <Buffer >,
    _closeTimer: null,
    _errorEmitted: true,
    _extensions: {},
    _paused: false,
    _protocol: '',
    _readyState: 3,
    _receiver: null,
    _sender: null,
    _socket: null,
    _bufferedAmount: 0,
    _isServer: false,
    _redirects: 0,
    _autoPong: true,
    _url: 'wss://localhost/v2',
    _req: null,
    [Symbol(shapeMode)]: false,
    [Symbol(kCapture)]: false
  },
  [Symbol(kType)]: 'error',
  [Symbol(kError)]: AggregateError [ECONNREFUSED]:
      at internalConnectMultiple (node:net:1116:18)
      at afterConnectMultiple (node:net:1683:7)
      at TCPConnectWrap.callbackTrampoline (node:internal/async_hooks:130:17) {
    code: 'ECONNREFUSED',
    [errors]: [ [Error], [Error] ]
  },
  [Symbol(kMessage)]: ''
}

[denolfe]

try manually adding pg to your package file. seems like there's an issue when trying to import types from pg library.

yarn add pg

I'm not sure why this would help considering pg is not a dependency of the db-vercel-postgres package.

Looking into the actual issue, though

[denolfe]

Looks like there was an old drizzle issue here: drizzle-team/drizzle-orm#505

However, it looks like that should have been merged in and fixed.

[t0m3t0m3]

I have the same error testing Payload 3.0 with vercel postgres 😔

[denolfe]

I have reached out to Drizzle regarding this.

[christianalares]

Same error here. Does any one know if there is a workaround while the issue is being looked at?