supabase/supabase-js

Guides · Reference Docs

This monorepo contains the complete suite of Supabase JavaScript SDK:

This section outlines the scope of support for various runtime environments in Supabase JavaScript client.

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.

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.

All modern browsers are supported. We support browsers that provide native fetch API. For Realtime features, browsers must also support native WebSocket API.

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.

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.

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.

• 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

npm install @supabase/supabase-js

Read more in each package's README file.

We welcome contributions! Please see our Contributing Guide for details.

1. Fork the repository
2. Create a feature branch (git checkout -b feature/amazing-feature)
3. Make your changes and add tests
4. Run tests (pnpm nx affected --target=test)
5. Commit your changes (pnpm commit)
6. Push to your branch (git push origin feature/amazing-feature)
7. Open a Pull Request

• Follow conventional commits for commit messages
• Add tests for new functionality
• Update documentation for API changes
• Run pnpm nx format before committing
• Ensure all tests pass with pnpm nx affected --target=test

Testing varies per package. See the top-level TESTING.md for an overview and links to package-specific guides.

• Auth SDK - Authentication and user management
• Database SDK - Database queries and operations
• Realtime SDK - Real-time subscriptions
• Storage SDK - File upload and management
• Functions SDK - Edge Functions invocation
• Main SDK - Combined SDK

• Contributing - Development guidelines
• Release Workflows - Release and publishing process
• Migration Guide - Cross-cutting migration notes (per-package migrations live alongside each package under packages/core/<package>/migrations/)
• Security Policy - Vulnerability reporting and disclosure policy
• Securing your npm installs - Consumer-side guide to defending your install against npm supply-chain attacks

You can verify registry signatures and provenance attestations for installed packages using the npm CLI:

npm audit signatures

Quick example for a single package install:

npm install @supabase/auth-js
npm audit signatures

Example output:

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.

This project is licensed under the MIT License - see the LICENSE file for details.

• Documentation: supabase.com/docs
• Community: GitHub Discussions
• Issues: GitHub Issues
• Discord: Supabase Discord