Andrew

Same problem here. Given there are users that edit certain files under the amplify dir these will follow our coding style formatting and will automatically happen through CI/CD or tooling....

+2

+1 

+1 Running into this as well in 2024.

I also am getting this with a yarn berry (modern) project, I haven't added a new lambda function in a while but after performing the add function, I am unable...

FWIW As a workaround while we wait to get amplify updated to work with yarn modern. I created my own `yarn` script that works around this limitation. ``` #!/usr/bin/env node...

+1 See also https://github.com/aws-amplify/amplify-cli/issues/13377

Likewise, I am having a similar situation trying to get pnpm to be configured for Next.js SSR apps. The lack of clear documentation is causing us to spin wheels.

I am also getting this error. I've been going around and around on this for days. Amplify is simply unusable.

+1