Big News: Socket raises $60M Series C at a $1B valuation to secure software supply chains for AI-driven development.Announcement →
Sign In

@supabase/functions-js

Package Overview
Dependencies
Maintainers
15
Versions
352
Alerts
File Explorer

Advanced tools

License
Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@supabase/functions-js - npm Package Compare versions

Comparing version
2.106.2
 to
2.107.0-beta.0
+11
AGENTS.md
# Agent instructions for `@supabase/functions-js`
JavaScript SDK for invoking Supabase Edge Functions.
When helping a user work with this package:
- **Usage and quick start**: [`README.md`](./README.md)
- **Full API reference**: [`src/`](./src/) — every public method and type has TSDoc with `@example` blocks. Read the source for the canonical, version-pinned answer.
- **Migration notes**: [`migrations/`](./migrations/) — per-theme markdown files for changes that need caller action.
For broader Supabase guidance (docs site, MCP tools, schema and project workflows), use the centralized [Supabase agent skills](https://github.com/supabase/agent-skills): `npx skills add supabase/agent-skills`. Or pair with the Supabase MCP server via the [Supabase Plugin for AI Coding Agents](https://supabase.com/docs/guides/getting-started/plugins).
+25
migrations/README.md
# Migration notes for `@supabase/functions-js`
Each file in this directory describes one migration theme — what changed in `@supabase/functions-js`, who is affected, and what callers need to do.
Files are shipped with the npm package, so the migration notes you see here are pinned to the version of `@supabase/functions-js` you have installed. Upgrading the package brings the relevant migration notes along with it.
## How agents should use this directory
When helping a developer upgrade `@supabase/functions-js`:
1. Read the migration files in `node_modules/@supabase/functions-js/migrations/` for the version they have installed.
2. Cross-reference against the version they are upgrading to.
3. Apply the migration steps described in each relevant file.
## How humans should use this directory
Browse the files for the migration theme you care about. Each file is self-contained and explains its own scope, audience, and steps.
## File naming
One file per migration theme, named by topic rather than version (e.g. `<theme>.md`, kebab-case). A single version can ship multiple theme files; a single theme can span multiple versions. Each file documents its own `Since` / `Will require action by` version range internally.
## Cross-cutting migration notes
Migrations that span multiple Supabase packages (e.g. Node.js version drops, monorepo restructures) live in [`docs/MIGRATION.md`](../../../../docs/MIGRATION.md) at the repository root, not here. This directory is scoped to `@supabase/functions-js` only.
+1
-1
dist/main/version.d.ts

@@ -1,2 +0,2 @@

export declare const version = "2.106.2";
export declare const version = "2.107.0-beta.0";
//# sourceMappingURL=version.d.ts.map
+1
-1
dist/main/version.d.ts.map

@@ -1,1 +0,1 @@

{"version":3,"file":"version.d.ts","sourceRoot":"","sources":["../../src/version.ts"],"names":[],"mappings":"AAMA,eAAO,MAAM,OAAO,YAAY,CAAA"}
{"version":3,"file":"version.d.ts","sourceRoot":"","sources":["../../src/version.ts"],"names":[],"mappings":"AAMA,eAAO,MAAM,OAAO,mBAAmB,CAAA"}
+1
-1
dist/main/version.js

@@ -10,3 +10,3 @@ "use strict";

// - Ensuring build artifacts match the published package version
exports.version = '2.106.2';
exports.version = '2.107.0-beta.0';
//# sourceMappingURL=version.js.map
+1
-1
dist/main/version.js.map

@@ -1,1 +0,1 @@

{"version":3,"file":"version.js","sourceRoot":"","sources":["../../src/version.ts"],"names":[],"mappings":";;;AAAA,6EAA6E;AAC7E,gEAAgE;AAChE,uEAAuE;AACvE,iEAAiE;AACjE,kEAAkE;AAClE,iEAAiE;AACpD,QAAA,OAAO,GAAG,SAAS,CAAA"}
{"version":3,"file":"version.js","sourceRoot":"","sources":["../../src/version.ts"],"names":[],"mappings":";;;AAAA,6EAA6E;AAC7E,gEAAgE;AAChE,uEAAuE;AACvE,iEAAiE;AACjE,kEAAkE;AAClE,iEAAiE;AACpD,QAAA,OAAO,GAAG,gBAAgB,CAAA"}
+1
-1
dist/module/version.d.ts

@@ -1,2 +0,2 @@

export declare const version = "2.106.2";
export declare const version = "2.107.0-beta.0";
//# sourceMappingURL=version.d.ts.map
+1
-1
dist/module/version.d.ts.map

@@ -1,1 +0,1 @@

{"version":3,"file":"version.d.ts","sourceRoot":"","sources":["../../src/version.ts"],"names":[],"mappings":"AAMA,eAAO,MAAM,OAAO,YAAY,CAAA"}
{"version":3,"file":"version.d.ts","sourceRoot":"","sources":["../../src/version.ts"],"names":[],"mappings":"AAMA,eAAO,MAAM,OAAO,mBAAmB,CAAA"}
+1
-1
dist/module/version.js

@@ -7,3 +7,3 @@ // Generated automatically during releases by scripts/update-version-files.ts

// - Ensuring build artifacts match the published package version
export const version = '2.106.2';
export const version = '2.107.0-beta.0';
//# sourceMappingURL=version.js.map
+1
-1
dist/module/version.js.map

@@ -1,1 +0,1 @@

{"version":3,"file":"version.js","sourceRoot":"","sources":["../../src/version.ts"],"names":[],"mappings":"AAAA,6EAA6E;AAC7E,gEAAgE;AAChE,uEAAuE;AACvE,iEAAiE;AACjE,kEAAkE;AAClE,iEAAiE;AACjE,MAAM,CAAC,MAAM,OAAO,GAAG,SAAS,CAAA"}
{"version":3,"file":"version.js","sourceRoot":"","sources":["../../src/version.ts"],"names":[],"mappings":"AAAA,6EAA6E;AAC7E,gEAAgE;AAChE,uEAAuE;AACvE,iEAAiE;AACjE,kEAAkE;AAClE,iEAAiE;AACjE,MAAM,CAAC,MAAM,OAAO,GAAG,gBAAgB,CAAA"}
+4
-2
package.json
{
"name": "@supabase/functions-js",
"version": "2.106.2",
"version": "2.107.0-beta.0",
"description": "JS SDK to interact with Supabase Functions.",

@@ -21,3 +21,5 @@ "main": "dist/main/index.js",

"dist",
"src"
"src",
"migrations",
"AGENTS.md"
],

@@ -24,0 +26,0 @@ "license": "MIT",

+1
-1
src/version.ts

@@ -7,2 +7,2 @@ // Generated automatically during releases by scripts/update-version-files.ts

// - Ensuring build artifacts match the published package version
export const version = '2.106.2'
export const version = '2.107.0-beta.0'
dist/tsconfig.module.tsbuildinfo

Sorry, the diff of this file is not supported yet

dist/tsconfig.tsbuildinfo

Sorry, the diff of this file is not supported yet