Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Angular Tutorial Deploy Fail #7624

Open
BCusack opened this issue May 19, 2024 · 2 comments
Open

Angular Tutorial Deploy Fail #7624

BCusack opened this issue May 19, 2024 · 2 comments

Comments

@BCusack
Copy link

BCusack commented May 19, 2024

Environment information

System:
  OS: Windows 11 10.0.26120
  CPU: (20) x64 12th Gen Intel(R) Core(TM) i7-12700H
  Memory: 1.14 GB / 15.71 GB
Binaries:
  Node: 20.12.0 - C:\Program Files\nodejs\node.EXE
  Yarn: 1.22.19 - ~\AppData\Roaming\npm\yarn.CMD
  npm: 10.8.0 - C:\Program Files\nodejs\npm.CMD
  pnpm: undefined - undefined
NPM Packages:
  @aws-amplify/backend: 1.0.0
  @aws-amplify/backend-cli: 1.0.1
  aws-amplify: 6.3.2
  aws-cdk: 2.140.0
  aws-cdk-lib: 2.140.0
  typescript: 5.4.5
AWS environment variables:
  AWS_NODEJS_CONNECTION_REUSE_ENABLED = 1
  AWS_SDK_LOAD_CONFIG = 1
  AWS_STS_REGIONAL_ENDPOINTS = regional
No CDK environment variables

Description

During the Amplify Gen 2 Angular Quick start at step 6. Implement login UI. The deployment fails due to low production budget threshold in the Angular.json

         "configurations": {
           "production": {
             "budgets": [
               {
                 "type": "initial",
                 "maximumWarning": "500kb",
                 "maximumError": "1mb"
               },

A mention of this would be handy to users
main-2OXBZKPV.js | main | 739.26 kB | 178.16 kB
styles-B2HMUAM4.css | styles | 270.78 kB | 20.75 kB
polyfills-S3BTP7ME.js | polyfills | 33.24 kB | 10.76 kB
| Initial total | 1.02 MB | 209.67 kB

@ykethan
Copy link
Contributor

ykethan commented May 20, 2024

Hey, thanks for raising this! I'm going to transfer this over to our documentation repository to track this.

@ykethan ykethan transferred this issue from aws-amplify/amplify-backend May 20, 2024
@jpangburn
Copy link
Contributor

I ran into this problem as well. It's easy to resolve, but will cause new users some friction. In case it's not obvious to anyone who finds this looking for a solution, from @BCusack 's comment you just edit maximumError to be larger, like 2mb. Commit the change to your repository and Amplify will redeploy successfully.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants