This repository was archived by the owner on Jul 7, 2020. It is now read-only.
Updates aws-amplify/cli npm path in README #16
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
Needs `@` prefix in order to install properly, according to [aws-amplify/amplify-cli](https://github.com/aws-amplify/amplify-cli).
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
Needs
@prefix in order to install properly, according to aws-amplify/amplify-cli.Issue #, if available:
Description of changes:
When trying to install without the
@prefix, NPM fails. Could be a versioning issue on my machine, but the official docs for theamplify-cliuses the@prefix. This update makes both npm paths match.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.