Latest version 4.13.3-- can not init due to plugins error.

Note: If your issue/bug is regarding the AWS Amplify Console service, please log it in the Amplify Console GitHub Issue Tracker

Describe the bug Upgraded to aws-amplify/cli@4.13.3.

Attempt to init a new gatsby project to upload it to amplify fails with the following–

Error: Found no provider plugins Run ‘amplify plugin scan’ to scan your system for provider plugins. init failed

Scanning for plugins… The following official plugins are missing or inactive: awscloudformation: provider | amplify-provider-awscloudformation@4.13.3 codegen: util | amplify-codegen@2.13.3 mock: util | amplify-util-mock@3.14.0 Plugin scan successful

To my knowledge, there should have been no change to these plugins as they worked the last 72 hours.

Amplify CLI Version You can use amplify -v to check the amplify cli version on your system

4.3.3

To Reproduce Steps to reproduce the behavior or terminal output if applicable

amplify init

Expected behavior A clear and concise description of what you expected to happen.

Expect to complete init without error as I have done the last few weeks and then setup git push to deliver to amplify

Screenshots If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. Mac/Windows/Ubuntu]
• Node Version. You can use node -v to check the node version on your system

Ubuntu 19.04, node version 12.15.0

Additional context Have tried re-installing aws-amplify/cli, reinstalled all node_modules (local). I saw in prior errors of this kind on windows, users had to manually link plugins giving file path and name. I didn’t see similar way to do on linux.

[photon-garden]

Could we add a note to the docs specifying that you must use npm and must install the CLI globally? In the JS ecosystem, you can normally use yarn or npm as you please, and install globally or locally, so this behavior is quite confusing.

[weisisheng]

After about 6 hours of grubbing around, found this recommendation, #2746. Removing the yarn global dir and reinstalling using npm seems to fix my problem. Ugh.