mirror of
https://github.com/supabase/supabase.git
synced 2026-05-06 22:18:00 +08:00
9819fb7b20
## I have read the [CONTRIBUTING.md](https://github.com/supabase/supabase/blob/master/CONTRIBUTING.md) file. YES ## What kind of change does this PR introduce? Docs update ## What is the current behavior? [Edge function docs state:](https://supabase.com/docs/guides/functions/limits#:~:text=Maximum%20Function%20Size%3A%2020MB%20(After%20bundling%20using%20CLI))> Maximum Function Size: 20MB (After bundling using CLI) However, the bundle size troubleshooting guide argues: > Edge Functions have a 10MB source code limit. If your function exceeds this limit, deployment will fail. ## What is the new behavior? Updated the 10MB limit to 20MB in the troubleshooting docs
56 lines
1.6 KiB
Plaintext
56 lines
1.6 KiB
Plaintext
---
|
|
title = "Edge Function bundle size issues"
|
|
topics = [ "functions" ]
|
|
keywords = [ "bundle", "size", "limit", "dependencies", "edge function", "10MB" ]
|
|
database_id = "aaf9e673-64ae-460a-88e0-b83ea4963382"
|
|
|
|
[api]
|
|
cli = [ "supabase-functions-deploy" ]
|
|
---
|
|
|
|
Edge Functions have a 20MB source code limit. If your function exceeds this limit, deployment will fail.
|
|
|
|
## Check your bundle size
|
|
|
|
Use the `deno info` command to analyze your function's dependencies and total size:
|
|
|
|
```bash
|
|
deno info /path/to/function/index.ts
|
|
```
|
|
|
|
Look for the "size" field in the output to see the total bundle size.
|
|
|
|
## How to reduce bundle size
|
|
|
|
If your bundle is too large, try these strategies:
|
|
|
|
### Remove unused dependencies
|
|
|
|
Review your imports and remove any packages you're not actively using.
|
|
|
|
### Use selective imports
|
|
|
|
Instead of importing entire packages, import only the specific modules you need:
|
|
|
|
```tsx
|
|
// Good: Import specific submodules
|
|
import { specific } from 'npm:package/specific'
|
|
|
|
// Avoid: Import entire package
|
|
import * as everything from 'npm:package'
|
|
```
|
|
|
|
### Split large functions
|
|
|
|
Consider breaking large functions into smaller, more focused functions. Each function can handle a specific task, reducing the code needed in any single deployment.
|
|
|
|
### Choose lightweight alternatives
|
|
|
|
Research smaller packages that provide the same functionality. Many NPM packages designed for Node.js include unnecessary polyfills that increase bundle size.
|
|
|
|
## Additional resources
|
|
|
|
- [Unable to deploy Edge Function](./unable-to-deploy-edge-function)
|
|
- [Dependency analysis](./edge-function-dependency-analysis)
|
|
- [Edge Function limits](/docs/guides/functions/limits)
|