aws-amplify / aws-amplify/amplify-cli

`amplify build` exits with no notification of success

Open
#12,130 1 comment 0 reactions 0 assignees View on GitHub
bug good first issue p3 platform-build
Dominant language
TypeScript
Stars
2.9k
Forks
825
Avg merge
11d 23h
Merged PRs (30d)
2

Description

### How did you install the Amplify CLI?

pnpm

### If applicable, what version of Node.js are you using?

18

### Amplify CLI Version

11.0.0-beta.8

### What operating system are you using?

mac

### Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.

n/a

### Describe the bug

When running `amplify build`, successful builds do not show what resources were built, nor a "success" message

### Expected behavior

```
➜ amplify build
Success!
```

or

```
➜ amplify build
Successfully built:

- myapi (GraphQL API)
- myfunction (Function)
- myauth (Auth)
```

### Reproduction steps

1. `amplify init -y`
2. add some resources, maybe an override
3. `amplify build`

### Project Identifier

_No response_

### Log output

```
# Put your logs below this line

```

### Additional information

_No response_

### Before submitting, please confirm:

- [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.

Contributor guide

Open the contributing guide

Research direction

Reproduce the issue with `amplify init -y`, add resources or an override, and run `amplify build` on the reported CLI setup. Trace the `amplify build` command entry point to determine why a successful build emits no summary; done means a successful build clearly reports success and, where applicable, the resources built.

Written by the indexing model from the issue text.

Assessment

Tech stack
node.js, typescript
Domain
cli
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.