The Edge Function size exceeds 1MB

[vignesh-gupta]

Summary

Using hono with nextjs from this doc, Started getting the size limit exceeded after this commit. Which has nothing to do with api route.

Additional information

Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 11 Home Single Language
  Available memory (MB): 7540
  Available CPU cores: 12
Binaries:
  Node: 20.18.0
  npm: 10.9.0
  Yarn: 1.22.22
  pnpm: 9.14.2
Relevant Packages:
  next: 15.1.3 // Latest available version is detected (15.1.3).
  eslint-config-next: N/A
  react: 19.0.0
  react-dom: 19.0.0
  typescript: N/A
Next.js Config:
  output: N/A

Example

https://github.com/vignesh-gupta/clikz/

[icyJoseph]

Could you make a build with, https://www.npmjs.com/package/@next/bundle-analyzer activated, and see what the Edge Report (three reports open, one for your Node env, one for the browser, and one for the Edge), is showing as included?

[vignesh-gupta]

From what I see, the both cases there are 2 major packages

1. Next, react, react-dom
2. prisma

Also I'll create a issue on vercel platform too for gzip size issue

[icyJoseph]

I wonder, if you could use, https://nextjs.org/docs/app/api-reference/config/next-config-js/output#caveats outputFileTracingExcludes on your route, to drop some unused stuff

[vignesh-gupta]

@icyJoseph also how can I raise the issue for vercel team to take a look?

And I've hono with next js in another project too, which has more endpoint but works fine.

I managed to remove Prisma from middleware and reduce the size but still it's .09 MB extra. And didn't find any issues with hono either for import export.

[icyJoseph]

I think you can either submit a support ticket, or go to the Vercel cli repository, called Vercel.

Good that you narrowed down the size though.

[icyJoseph]

btw, may I ask why do you need a manual stable sort? AFAIK, V8, introduced stable sort back in 2019: https://v8.dev/features/stable-sort

Is there other engines you know of, which do not have stable sort? Would like to know more.