Hi there,
I understand how frustrating it can be to face build size limitations, especially when it impacts your ability to update your project. Regarding Vercel, it does not impose a strict build size limit like AWS Amplify. However, there are some general guidelines and constraints to keep in mind when deploying a Next.js project on Vercel:
-
Build Execution:
- Vercel uses serverless functions to build your project, and the individual function size is limited to 50 MB uncompressed (which includes the code and dependencies).
- However, the total project build output (including static files) is not strictly capped unless you're using a free plan, where limits on bandwidth and storage apply.
-
Optimization for Larger Builds:
- If your project is growing in size due to a large number of pages or Next.js upgrades, you can implement Incremental Static Regeneration (ISR) or Dynamic Routing to reduce the build size.
- Splitting static files or lazy-loading components can also help optimize deployment.
-
Support for Growing Projects:
- Vercel scales well with large Next.js projects, making it a suitable alternative for your growing application.
Since your business is being negatively affected, I’d recommend reaching out directly to Vercel's support team for personalized guidance, especially if your project has unique constraints or enterprise-level needs.
Migrating from AWS Amplify to Vercel could be a good solution given the flexibility it offers, but do review their pricing tiers and bandwidth limits if you anticipate high traffic or large-scale usage.
Let me know if you need help with the migration process!
Wishing you a smooth transition and quick resolution.
Cheers,