chore: move packaged dependencies to dev dependencies#5264
Merged
Conversation
jgoux
commented
May 18, 2026
Contributor
Author
There was a problem hiding this comment.
This is the important change, we're moving all dependencies as dev dependencies as they're packaged in the final Bun binary and we don't want them to end up in node_modules when the users do npm install
avallete
approved these changes
May 18, 2026
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
2 participants
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.
What changed
This updates the published
supabasenpm package so it behaves as a lightweight shim package. The package now shipsdist/supabase.jsand declares only the platform-specific@supabase/cli-*packages as optional runtime dependencies. The CLI runtime dependencies are kept as development dependencies because the compiled Bun binaries already contain what they need.The dependency catalog and lockfile were refreshed alongside that packaging change, including aligning the Effect platform packages on the same beta. To keep the workspace green with those updates, the TypeScript code was migrated to the newer Effect service APIs (
Context.Service), schema decoding defaults were updated for the current Schema API, and mock child process handles now implement the requiredunrefmember.The PR also updates the vendored
.repos/*snapshots that were staged for this branch.