Code:400 Message:The function exceeds the maximum size of 250 MB

My website URL is: learn-less.netlify.app
My deploy url:
Netlify
Here’s the build log:

1:06:26 AM: ​
1:06:26 AM: ❯ Version
1:06:26 AM: @netlifynetlifynetlifynetlifynetlifynetlifynetlifynetlify/build 35.13.4
1:06:26 AM: ​
1:06:26 AM: ❯ Flags
1:06:26 AM: accountId: 62701a49b23d2106e7ffca08
1:06:26 AM: baseRelDir: true
1:06:26 AM: buildId: 6a0b54fa229ba50007aa7463
1:06:26 AM: deployId: 6a0b54fa229ba50007aa7465
1:06:26 AM: ​
1:06:26 AM: ❯ Current directory
1:06:26 AM: /opt/build/repo
1:06:26 AM: ​
1:06:26 AM: ❯ Config file
1:06:26 AM: /opt/build/repo/netlify.toml
1:06:26 AM: ​
1:06:26 AM: ❯ Context
1:06:26 AM: deploy-preview
1:06:26 AM: ​
1:06:26 AM: ❯ Installing extensions
1:06:26 AM: - user-agent-blocker
1:06:28 AM: ​
1:06:28 AM: ❯ Loading extensions
1:06:28 AM: - user-agent-blocker
1:06:29 AM: ​
1:06:29 AM: build.command from netlify.toml
1:06:29 AM: ────────────────────────────────────────────────────────────────
1:06:29 AM: ​
1:06:29 AM: $ npm run build
1:06:29 AM: > learn-less@1.0.0 build
1:06:29 AM: > vite build

1:07:04 AM: ✓ built in 34.03s
1:07:04 AM: Run npm run preview to preview your productio@sveltejsUsing1 build locally.
1:07@sveltejsUsing0@sveltejs AM:@sveltejsUsing1@sveltejs07:04 AM: >@sveltejsUsing @sveltejs/adapter-netlify
1:07:04 AM: :check_mark: done
1:07:04 AM: ​
1:07:04 AM: (build.command completed in 35.7s)
1:07:05 AM: ​
1:07:05 AM: Functions bundling
1:07:05 AM: ────────────────────────────────────────────────────────────────
1:07:05 AM: ​
1:07:05 AM: Packaging Functions from .netlify/functions-internal directory:
1:07:05 AM: - sveltekit-render.mjs
1:07:05 AM: ​
1:07:28 AM: ​
1:07:28 AM: (Functions bundling completed in 23.9s)
1:07:28 AM: ​
1:07:28 AM: Deploy site
1:07:28 AM: ────────────────────────────────────────────────────────────────
1:07:28 AM: ​
1:07:28 AM: Starting to deploy site from ‘build’
1:07:29 AM: Calculating files to upload
1:07:29 AM: 51 new file(s) to upload
1:07:29 AM: 1 new function(s) to upload
1:07:37 AM: The function exceeds the maximum size of 250 MB
1:07:37 AM: Failed to upload file: sveltekit-render
1:07:37 AM: Section completed: deploying
1:07:37 AM: ​
1:07:37 AM: Error deploying
1:07:37 AM: ────────────────────────────────────────────────────────────────
1:07:37 AM: ​
1:07:37 AM: Error message
1:07:37 AM: Deploy did not succeed with HTTP Error 400: [PUT /deploys/{deploy_id}/functions/{name}][400] uploadDeployFunction default &{Code:400 Message:The function exceeds the maximum size of 250 MB@huggingfaceM

1:07:37 AM: functions:
1:07:37 AM: "*@huggingfaceM:
1:07:37 AM:@huggingface @huggingfaceM external_n@@googleapisuggingfacede_modules:
1:07:37 @huggingfaceM: - “@@googleapisuggingface/transformers”
1:07:37 AM: @googleapis - onnxruntime-no@googleapise
1:07:37 AM: - “@googleapis/calendar”
1:07:37 A@huggingface: - google-auth-library
1:07:3@huggingface AM: ignored_n@huggingfacede_modules:
1:07:37 AM: - “@huggingface/transformers”
1:07:37 AM: - onnxruntime-node
1:07:37 AM: - “@googleapis/calendar”
1:07:37 AM: - google-auth-library
1:07:37 AM: node_bundler: esbuild
1:07:37 AM: headers:
1:07:38 AM: Failed during stage ‘building site’: Build script returned non-zero exit code: 2 ( Search results for '"non-zero exit code: 2"' - Netlify Support Forums )
1:07:38 AM: - for: /_app/immutable/*
values:
cache-control: public, immutable, max-age=31536000
1:07:38 AM: Build failed due to a user error: Build script returned non-zero exit code: 2
1:07:38 AM: Failing build: Failed to build site
1:07:38 AM: Finished processing build request in 1m51.473s

Hey @wentallout :wave:,
Thanks for reaching out!

We’ve gone ahead and created a support ticket for you, so our team can follow up with you directly via email from the help desk. Our Support crew will be in touch with you by email soon.

Great news: these days anyone can reach out to Netlify Support. First, you can try getting an answer using Ask Netlify, our helpful AI search tool. If your question isn’t answered there, you can submit a ticket using the support form, and we’ll take it from there.

We’re keeping the community around for swapping ideas, sharing tips and tricks, and talking shop with other folks building on the platform — but for support issues, tickets are the way to go.

Thanks for being here, and keep an eye out for that email from us!