Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: supabase/supabase-js
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v2.53.0
Choose a base ref
...
head repository: supabase/supabase-js
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v2.53.1
Choose a head ref
  • 1 commit
  • 2 files changed
  • 1 contributor

Commits on Aug 7, 2025

  1. fix: avoid Next.js Edge Runtime warnings in Node.js deprecation check (… 

    …#1520)

* fix: avoid Next.js Edge Runtime warnings in Node.js deprecation check

Use dynamic property access for process.version to prevent Next.js static
analysis from flagging the code as incompatible with Edge Runtime.

The deprecation warning logic remains unchanged - it only runs in actual
Node.js environments and is properly guarded against Edge Runtime execution.

Fixes #1515

* fix: restore undefined and null checks for process.version

Maintain the original defensive programming checks while still using
dynamic property access to avoid Edge Runtime warnings

* test: add comprehensive tests for Node.js deprecation warning

- Test browser environment detection
- Test Edge Runtime compatibility (no process object)
- Test various process.version states (undefined, null, invalid)
- Test version detection for Node.js 16, 18, 20, 22
- Test invalid version format handling

* fix: update deprecation tests to work with TypeScript isolatedModules

- Add export {} to make file a module
- Remove problematic test for undefined process (dependencies require it)
- Add comment explaining why Edge Runtime scenario is hard to test in Node

* test: eliminate TTYWRAP warnings in deprecation tests

Use Object.defineProperty to mock only process.version instead of
spreading the entire process object. This avoids copying TTY handles
and other complex properties that cause Jest warnings.
    @mandarini
    mandarini authored Aug 7, 2025
    Configuration menu
    Copy the full SHA
    4f38a9c View commit details
    Browse the repository at this point in the history
Loading