MJ Zhang
MJ Zhang
Thanks. The time range in the command was incorrect, which is 2021, but supposed to be 2022.
It was greyed out (disabled), but when it's enabled again, the issue mentioned above happened.
Hello @BBopanna , To answer your questions, 1. Why there are 3 packages? [`aws-amplify-react`](https://www.npmjs.com/package/aws-amplify-react) is a deprecated package, which stoped updated since 8 month ago. [@aws-amplify/ui-react](https://www.npmjs.com/package/@aws-amplify/ui-react) is the Amplify UI...
Might be related to https://github.com/aws-amplify/amplify-cli/issues/9386
Thanks for following up. I found it was `cy.request` takes a lot of memory. So I reduced `cy.request` usage and also use `HEAD` instead of `GET`, which helped. My Mac...
`mock` doesn't work because our Go Runtime has already upgraded from go1.x (https://github.com/aws-amplify/amplify-cli/pull/13671), which means the RPC we use for `mock` doesn't work anymore. ref: - how we use RPC...
might be related to https://github.com/aws-amplify/amplify-cli/issues/9386
The error happens because Modern Yarn (2,3) doesn't create yarn.lock when running yarn install if it can find a yarn.lock in it's parent directory. Before the PR https://github.com/aws-amplify/amplify-cli/pull/13197 gets merged,...
Hi 👋 @martoncsikos Could you confirm the version? Is that 12.0.3 or 12.10.3? Have you happened to try 12.10.2 as well?
Thanks for catching the lambda layer increment. We are sorry that it bothers you. Here's what we found about the issue: - It happens on Amplify Hosting when deploying a...