aws-amplify / aws-amplify/amplify-hosting

Next.js 13 Amplify - CustomerError: The size of the build output exceeds the max allowed size of 230686720 bytes

Open
#3,863 35 comments 8 reactions 0 assignees View on GitHub
pending-triage
Dominant language
Dockerfile
Stars
481
Forks
123
PR merge metrics
No merged PRs in 30d

Description

### Before opening, please confirm:

- [X] I have checked to see if my question is addressed in the [FAQ](https://github.com/aws-amplify/amplify-hosting/blob/master/FAQ.md).
- [X] I have [searched for duplicate or closed issues](https://github.com/aws-amplify/amplify-hosting/issues?q=is%3Aissue+).
- [X] I have read the guide for [submitting bug reports](https://github.com/aws-amplify/amplify-hosting/blob/master/CONTRIBUTING.md).
- [X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
- [X] I have removed any sensitive information from my code snippets and submission.

### App Id

new_app

### AWS Region

us-east-1

### Amplify Hosting feature

Frontend builds

### Frontend framework

Next.js

### Next.js version

13

### Next.js router

App Router

### Describe the bug

https://github.com/aws-amplify/amplify-hosting/issues/3647

Issue above has been abruptly closed without providing any details .. Creating this new ticket

200MB limit is still there : why can it not be removed?

### Expected behavior

Build should not fail

### Reproduction steps

Build
Front end build steps fails ;:

### Build Settings

_No response_

### Log output

```
# Put your logs below this line
2023-12-19T07:14:02.836Z [INFO]: # Caching completed
2023-12-19T07:14:19.932Z [ERROR]: !!! CustomerError: The size of the build output (236302771) exceeds the max allowed size of230686720 bytes. Please reduce the size ofyour build output and try again.

```

### Additional information

_No response_

Contributor guide

Open the contributing guide

Research direction

Start by reviewing FAQ.md and CONTRIBUTING.md, then inspect the referenced issue 3647 and the reported build log. The payload does not identify a repository file, test, build configuration, or code entry point to change; the issue would need a confirmed owner and a defined solution for the 230686720-byte hosting limit before implementation can begin.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, next.js
Domain
ci-cd, cloud
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.