This section outlines the scope of support for various runtime environments in Supabase JavaScript client.
Node.js
We only support Node.js versions that are in Active LTS or Maintenance status as defined by the official Node.js release schedule. This means we support versions that are currently receiving long-term support and critical bug fixes.
When a Node.js version reaches end-of-life and is no longer in Active LTS or Maintenance status, Supabase will drop it in a minor release, and this won’t be considered a breaking change.
⚠️ Node.js 18 Deprecation Notice
Node.js 18 reached end-of-life on April 30, 2025. As announced in our deprecation notice, support for Node.js 18 was dropped in version 2.79.0.
If you must use Node.js 18, please use version 2.78.0, which is the last version that supported Node.js 18.
⚠️ Node.js 20 Deprecation Notice
Node.js 20 reached end-of-life on April 30, 2026. As announced in our deprecation notice, support for Node.js 20 was dropped in version 2.110.0.
If you must use Node.js 20, please use version 2.109.0, which is the last version that supported Node.js 20.
Deno
We support Deno versions that are currently receiving active development and security updates. We follow the official Deno release schedule and only support versions from the stable and lts release channels.
When a Deno version reaches end-of-life and is no longer receiving security updates, Supabase will drop it in a minor release, and this won’t be considered a breaking change.
Browsers
All modern browsers are supported. We support browsers that provide native fetch API. For Realtime features, browsers must also support native WebSocket API.
Bun
We support Bun runtime environments. Bun provides native fetch support and is compatible with Node.js APIs. Since Bun does not follow a structured release schedule like Node.js or Deno, we support current stable versions of Bun and may drop support for older versions in minor releases without considering it a breaking change.
React Native
We support React Native environments with fetch polyfills provided by the framework. Since React Native does not follow a structured release schedule, we support current stable versions and may drop support for older versions in minor releases without considering it a breaking change.
Cloudflare Workers
We support Cloudflare Workers runtime environments. Cloudflare Workers provides native fetch support. Since Cloudflare Workers does not follow a structured release schedule, we support current stable versions and may drop support for older versions in minor releases without considering it a breaking change.
Important Notes
Experimental features: Features marked as experimental may be removed or changed without notice
Build warnings: If you see UNUSED_EXTERNAL_IMPORT warnings from Vite/Nuxt, see the supabase-js README — these are false positives
Supabase Service Compatibility
The Supabase JavaScript SDK only guarantees compatibility with the latest
release of each Supabase service, unless a minimum supported version is
explicitly listed below.
Older service releases are supported on a best-effort basis, but compatibility
is not guaranteed.
If you self-host Supabase, we recommend upgrading your services to their latest
releases when upgrading the SDK.
Where a lowest supported version is listed, some features still need a newer
server version. Those requirements are noted in the API reference for the
feature.
🚀 Quick Start
Installation
npm install @supabase/supabase-js
Read more in each package’s README file.
🤝 Contributing
We welcome contributions! Please see our Contributing Guide for details.
Quick Contribution Steps
Fork the repository
Create a feature branch (git checkout -b feature/amazing-feature)
Make your changes and add tests
Run tests (pnpm nx affected --target=test)
Commit your changes (pnpm commit)
Push to your branch (git push origin feature/amazing-feature)
audited 1 package in 0s
1 package has a verified registry signature
Because provenance attestations are a new capability, security features may evolve over time. Ensure you are using the latest npm CLI to verify attestation signatures reliably. This may require updating npm beyond the version bundled with Node.js.
For a broader checklist — minimum release age, lockfile hygiene, blocking exotic transitive deps, lifecycle script controls, and what to do if you suspect a compromise — see Securing your npm installs.
📄 License
This project is licensed under the MIT License - see the LICENSE file for details.
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?v=4)
评论