drizzle-team / drizzle-team/drizzle-orm

[BUG]: Migration uses `neon-serverless` locally

Open
#3,211 3 comments 1 reaction 0 assignees View on GitHub
db/postgres drizzle/kit improvement priority
Dominant language
TypeScript
Stars
35.8k
Forks
1.6k
Avg merge
2d 7h
Merged PRs (30d)
4

Description

### What version of `drizzle-orm` are you using?

?

### What version of `drizzle-kit` are you using?

?

### Describe the Bug

From drizzle-kit-mirror repo: https://github.com/drizzle-team/drizzle-kit-mirror/issues/576.

> I'm trying to run migration locally, but `drizzle-kit migrate` uses `neon-serverless` even if it's not defined anywhere. I have a local postgresql database with no web socket connections or neon-related stuff. Is it possible to use `pg` or so locally, but `neon-serverless` in production? Or define custom `wsProxy` in the local environment during migration?

### Expected behavior

_No response_

### Environment & setup

_No response_

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.