amplify-cli: Amplify version cli 11 breaks cicd with `No package manager found.`

How did you install the Amplify CLI?

npm

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

16.0.0

Amplify CLI Version

11.0.0

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.

No manual changes made

Describe the bug

Running the amplify CI/CD in the amplify console with amplify cli version 11 breaks the CI/CD

                                    - Building custom resources
2023-03-13T22:54:14.709Z [WARNING]: ✖ There was an error initializing your environment.
2023-03-13T22:54:14.710Z [INFO]: 🛑 No package manager found.
                                 Resolution: Install npm or yarn to compile overrides for this project.
                                 Learn more at: https://docs.amplify.aws/cli/project/troubleshooting/
2023-03-13T22:54:14.728Z [INFO]: 
2023-03-13T22:54:14.728Z [INFO]: Session Identifier: 1d05c407-17d0-479f-9c09-aa6c69927f19
2023-03-13T22:54:14.753Z [ERROR]: !!! Build failed
2023-03-13T22:54:14.753Z [ERROR]: !!! Non-Zero Exit Code detected
2023-03-13T22:54:14.753Z [INFO]: # Starting environment caching...
2023-03-13T22:54:14.753Z [INFO]: # Environment caching completed
Terminating logging...

Expected behavior

I expect the CI/CD pipeline to work. K thanks bye

Reproduction steps

  1. Run a new build with amplify CLI version 11
  2. Watch the build run till the backend build hits the error
  3. Thanks

Project Identifier

No response

Log output

dsaf

Additional information

fsda

Before submitting, please confirm:

  • I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
  • I have removed any sensitive information from my code snippets and submission.

About this issue

  • Original URL
  • State: closed
  • Created a year ago
  • Reactions: 6
  • Comments: 24 (14 by maintainers)

Most upvoted comments

Version 11.0.1 was shipped with a fix for No package manager found. problem.

We also had this issue, rolling back to 10.8.1 fixed it. The logs were unhelpful.