Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Amplify CLI Plugin Scan Failed
See original GitHub issueNote: If your question is regarding the AWS Amplify Console service, please log it in the official AWS Amplify Console forum
Which Category is your question related to? Amplify CLI Plugin scan failed.
Amplify CLI Version
You can use amplify -v to check the amplify cli version on your system
~/D/4/taskmaster notifications ± amplify -v Scanning for plugins… Plugin scan failed. Plugin scan failed. Error: Plugin scan failed. at scan (/usr/local/lib/node_modules/@aws-amplify/cli/src/plugin-manager.ts:137:11) ~/D/4/taskmaster notifications ±
What AWS Services are you utilizing?
Provide additional details e.g. code snippets
I uninstalled and reinstalled Amplify CLI. Keep getting the same errors over and over.
~/D/4/taskmaster notifications ± amplify -v Scanning for plugins… Plugin scan failed. Plugin scan failed. Error: Plugin scan failed. at scan (/usr/local/lib/node_modules/@aws-amplify/cli/src/plugin-manager.ts:137:11) ~/D/4/taskmaster notifications ±
Issue Analytics
- State:
- Created 4 years ago
- Reactions:2
- Comments:21 (7 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Or, simply
I’m having the same issue as OP. Node version: 12.16.1 NPM version: 6.13.14 yarn version: 1.22.0 OS: Windows 10 Home, Version 1809, OS Build 17763.1039
I installed the amplify cli in my root directory C:\npm install -g @aws-amplify/cli I successfully got to the post-install.js, “Successfully installed the Amplify CLI…Javascript Getting Started…”. Anytime I run an amplify command, I receive the same error as OP. This includes amplify init, amplify -v, etc. This is the same error whether I run them in the root directory or my project directory.
I’ve tried reinstalling node, npm, yarn, webstorm, and amplify, and have also deleted and re-cloned my project from github. The set-up has worked for other members of my team without issue, but does not work on my environment, although it was working roughly 2 months ago when we began the project. Error started last week when we re-visited the project (I did have to pull it from master this time around.)
Willing to provide any other information necessary to assist with troubleshooting 😃