feat: use pglite to avoid requiring postgres when generating types#36
Open
MrAnderson323 wants to merge 7 commits into
Open
feat: use pglite to avoid requiring postgres when generating types#36MrAnderson323 wants to merge 7 commits into
MrAnderson323 wants to merge 7 commits into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When running
bun run db:generate, users no longer need a running PostgreSQL instance. Instead, the type generation process spins up an in-process PGlite instance, applies the schema migrations, introspects the resulting schema, and generates types — all without any external dependencies.This uses
@electric-sql/pgliteto run an ephemeral in-memory PostgreSQL-compatible database for schema introspection during type generation.Closes #2