initTriggerEnvs path issue, no such file or directory

Describe the bug I am contributing to an existing Amplify project. I download the source code and run amplify init. In the process It asks if I want to create a Lambda. Regardless of my answer I get the error Error: ENOENT: no such file or directory, open referring to .nvm/versions/node/v10.17.0/lib/node_modules/@aws-amplify/cli/node_modules/amplify-category-function/lib/provider-utils/awscloudformation/../../../amplify-category-auth/provider-utils/awscloudformation/triggers/PreTokenGeneration/PreTokenGeneration.map.json

I installed amplify 4.16.1 and the bug does not exist.

Amplify CLI Version 4.17.1

To Reproduce Create a working project with a version prior to 4.17.x or have an existing working Amplify project, then in a new account on a new machine, download the source code from the working project and initialize the project. Answer N when it asks to create the Lambda.

Expected behavior I expect the project to successfully initialize when I provide an appropriate response. In this project I expect the N response to successfully complete the initialization

Desktop (please complete the following information):

• OS: Mac
• Node Version: v10.17.0

[no-creative-name]

I have the same problem, just with the CustomMessage trigger.

Error: ENOENT: no such file or directory, open 'C:\Users\timo.mayer\AppData\Roaming\npm\node_modules\@aws-amplify\cli\node_modules\amplify-category-function\lib\provider-utils\awscloudformation/../../../amplify-category-auth/provider-utils/awscloudformation/triggers/CustomMessage/CustomMessage.map.json'

[github-actions[bot]]

This issue has been automatically locked since there hasn’t been any recent activity after it was closed. Please open a new issue for related bugs.

Looking for a help forum? We recommend joining the Amplify Community Discord server *-help channels for those types of questions.