Stuck on an issue?
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.
several non-multienv packages are downloaded, despite being specified as multienv
See original GitHub issueDescribe the bug
Installing @aws-amplify/cli@multienv with yarn results in several non-multienv packages being downloaded, resulting in faulty behavior.
To Reproduce
- Run
yarn global add @aws-amplify/cli@multienv - Go to global yarn directory (
yarn global bin) - Observe non-multienv version number in
node_modules/graphql-elasticsearch-transformer/package.json - Observe non-multienv version in global
yarn.lockentry forgraphql-elasticsearch-transformer
Expected behavior
Multienv versions of graphl-*-transformer packages should resolve to correct multienv versions.
Desktop (please complete the following information):
- OS: macos
Additional context
I have also tested with npm -g install @aws-amplify/cli@multienv and am observing similar results.
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Managing packages - Conda
Use the terminal or an Anaconda Prompt for the following steps. To install a specific package such as SciPy into an existing environment...
Read more >How to use yum to download a package without installing it
Confirm the RPM files are available in the specified download directory. Note: ... you can download multiple packages on the same command.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@thisjeremiah Just published a new version of the CLI (multienv tag) which fixes this issue.
@thisjeremiah There was an issue with publishing the multienv tag graphql-* packages. Looking into it.