drizzle-team / drizzle-team/drizzle-orm

[FEATURE]: make migrator work with drizzle proxy

Open
#4,290 1 comment 0 reactions 0 assignees View on GitHub
driver/http-proxy enhancement priority
Dominant language
TypeScript
Stars
35.8k
Forks
1.6k
Avg merge
2d 7h
Merged PRs (30d)
4

Description

### Feature hasn't been suggested before.

- [x] I have verified this feature I'm about to request hasn't been suggested before.

### Describe the enhancement you want to request

Currently the libsql migrator depends on node
https://github.com/drizzle-team/drizzle-orm/blob/a270acb6cf11078d09b0c6fb06ced4846cd1fdf6/drizzle-orm/src/libsql/migrator.ts#L6
https://github.com/drizzle-team/drizzle-orm/blob/a270acb6cf11078d09b0c6fb06ced4846cd1fdf6/drizzle-orm/src/migrator.ts#L1

In my scenario, I am writing a desktop app, I am using the proxy in frontend to execute sql queries in backend.
The migrator depends on node and cannot run in the frontend.

For now my only solution is to create a table to keep track of which migration files has been run and run the migration sql through proxy.

Contributor guide

Open the contributing guide

Research direction

Start with drizzle-orm/src/libsql/migrator.ts and drizzle-orm/src/migrator.ts to identify the Node dependencies that prevent frontend use. Compare those entry points with the Drizzle proxy execution scenario; the work is done when migrations can run through the proxy without requiring Node in the frontend.

Written by the indexing model from the issue text.

Assessment

Tech stack
node.js, typescript
Domain
database, desktop
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.