fix: require node >=22 to match @supabase/middleware - #132
Merged
Conversation
commit: |
mandarini
marked this pull request as ready for review
August 31, 2026 14:26
spydon
approved these changes
Aug 31, 2026
This was referenced Aug 31, 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.
Raises
engines.nodefrom>=20to>=22so the declared floor matches@supabase/middleware, a hard dependency since #88 that already requires Node>=22. Without this, 1.5.0 would install with EBADENGINE warnings on npm/pnpm and fail on Yarn 1 for Node 20 users, then break at runtime anyway.Non-breaking because no working configuration is lost: the dependency tree already enforces the
>=22floor transitively, so this change only makes the declaration match reality. Node 20 has also been end-of-life since April 2026.