fix(supabase): avoid edge runtime warnings in next.js #1998
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.
Summary
Fixes Edge Runtime warnings when using
supabase-jsin Next.js middleware.Problem
Next.js static analyzer detects usage of
process.versionsandprocess.versionin the built output and shows warnings duringnext build:process.versionsat line: 43) which is not supported in the Edge Runtimeprocess.versionat line: 389) which is not supported in the Edge RuntimeSolution
Use dynamic property access via
globalThisinstead oftypeof processchecks.The static analyzer cannot trace string-based property access, so it no longer flags these as Node.js API usage.
Before
After
Changes
packages/core/realtime-js/src/lib/websocket-factory.tspackages/core/supabase-js/src/index.tsRelated
Closes #1552