fix: use dynamic property access for proces.versions to avoid Edge Runtime warnings

[mandarini]

What kind of change does this PR introduce?

Bug fix - Eliminates Next.js Edge Runtime warnings

What is the current behavior?

Direct access to process.versions in websocket-factory.ts causes Next.js static analysis to flag the code as incompatible with Edge Runtime, even though the code is properly guarded and won't execute in Edge Runtime.

Fixes #523

What is the new behavior?

Uses dynamic property access (process['versions']) to avoid static analysis warnings while maintaining the same runtime behavior. The code still correctly detects Node.js versions and provides appropriate WebSocket implementations.

Additional context

• Same fix that was successfully applied to supabase-js in fix: avoid Next.js Edge Runtime warnings in Node.js deprecation check supabase-js#1520
• Related issue: Node.js 18 deprecation warning added in v2.52.1 causes Next.js Edge Runtime build warnings supabase-js#1515
• Added comprehensive tests for Edge Runtime compatibility and various Node.js version scenarios
• No breaking changes - purely an implementation detail to satisfy Next.js static analysis

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/@supabase/realtime-js@533

commit: fe3ca3f