A Serverless Function has exceeded the unzipped max size

I am including some large packages in my build, namely rehype-starry-night and /starty-night, and it seems to be inflating my build massively.

I can see in the build logs that there is a huge webpack cache being copied in, is there some way to ignore or exclude that? I’m confused about how to reduce this size.

Also, I’m confused why .git would be in there at all.

I think that just removing the .git directory would get these functions under the limit - are there any hooks I can tap into to remove that once the repo is cloned, before that gets unzipped into the different serverless functions?

Using bundle analyzer, here is the client bundle size: And nodejs bundle size:

I just don't understand how this could possibly be breaking a 250MB barrier!

Some more data:

Vercel CLI 39.3.0
WARNING: You should not upload the `.next` directory.
Installing dependencies...

up to date in 425ms

197 packages are looking for funding
  run `npm fund` for details
Detected Next.js version: 15.1.4
Running "npm run build"

> build
> next build

   ▲ Next.js 15.1.4
   - Experiments (use with caution):
     · turbo

   Creating an optimized production build ...
 ✓ Compiled successfully
 ✓ Linting and checking validity of types
 ✓ Collecting page data
 ✓ Generating static pages (42/42)
 ✓ Collecting build traces
 ✓ Finalizing page optimization

Route (app)                                            Size     First Load JS
┌ ○ /                                                  258 B           109 kB
├ ○ /_not-found                                        979 B           106 kB
├ ● /[slug]                                            141 B           105 kB
├   ├ /colophon
├   ├ /resume
├   └ /uses
├ ○ /feed.json                                         141 B           105 kB
├ ○ /feed.xml                                          141 B           105 kB
├ ● /posts/[slug]                                      231 B           109 kB
├   ├ /posts/2025-01-03-html-search-input
├   ├ /posts/2019-11-23-raspberry-pi-kiosk
├   ├ /posts/2018-12-29-screencasting-using-quicktime
├   └ [+13 more paths]
└ ● /posts/tagged/[slug]                               258 B           109 kB
    ├ /posts/tagged/javascript
    ├ /posts/tagged/gatsby
    ├ /posts/tagged/tools
    └ [+13 more paths]
+ First Load JS shared by all                          105 kB
  ├ chunks/4bd1b696-20882bf820444624.js                52.9 kB
  ├ chunks/517-4122b31d994211b5.js                     50.5 kB
  └ other shared chunks (total)                        1.89 kB


○  (Static)  prerendered as static content
●  (SSG)     prerendered as static HTML (uses generateStaticParams)

Traced Next.js server files in: 115.386ms
Created all serverless functions in: 886.539ms
Collected static files (public/, static/, .next/static): 2.171ms
✅  Build Completed in .vercel/output [17s]

➜ du -sh .vercel/output
6.8M    .vercel/output

I ended up adding the following to my next.config.js and got a build to succeed:

{
  outputFileTracingExcludes: {
    '/': ['.git', '.next/cache'],
    '/feed.xml': ['.git', '.next/cache'],
    '/feed.json': ['.git', '.next/cache'],
    '/\[slug\]': ['.git', '.next/cache'],
    '/posts/\[slug\]': ['.git', '.next/cache'],
    '/posts/tagged/\[slug\]': ['.git', '.next/cache'],
  },
}

It's unclear to me what I'm losing (if anything) by excluding these from tracing, but everything seems to be working.