amplify console build fail with <node-package-manager>.cmd --no-bin-links --production

[Lekha30]

How did you install the Amplify CLI?

curl

If applicable, what version of Node.js are you using?

19.6.0

Amplify CLI Version

12.2.5

What operating system are you using?

Mac

Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.

No changes made to the cloud resources managed by Amplify .

Describe the bug

amplify init stopped working all of a sudden.
I have various envrionments set up in amplify and has been working fine. All of a sudden amplify init stopped working. I am not able to do init. It is complaining of errors in the lambda layer.

Expected behavior

It should be updated to the env pointed out. amplify pull or amplify push not working either.

Reproduction steps

Checkout to a new amplify env
do amplify init

Project Identifier

No response

Log output

# Put your logs below this line

Additional information

No response

Before submitting, please confirm:

• I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
• I have removed any sensitive information from my code snippets and submission.

[Lekha30]

I was able to progress further by cleaning up all the node modules and temp folders. Amplify init works but amplify push is not working yet. Had some one faced this issue before?

[ykethan]

Hey @Lekha30, thank you for reaching out. The appears to be similar to #13043.
Could you try removing the .cmd in the amplify.state file in backend/function/<function-name> and retry pushing the project.

[Lekha30]

Awesome, that worked. Appreciate the timely help. Do you know why that got in the first place itself?

[ykethan]

Hey @Lekha30, was the function in the project created in a windows environment?
Looking at the code line it appears the npm.cmd gets added in a windows environment.

[ykethan]

marking this as bug for further improvements.

[ykethan]

Summary: A fix for functions with yarn package manager in windows was merged on #13047
Fix to address npm, pnpm package manager in windows: #13133

The PR: #13047 seems to also include a change on line to fix: #13001
the issue will need to be re-tested and closed if the behavior has been mitigated.

[qwikag]

For me this I had an extra function which I had not started using I had only created it: it had this amplify.state file:

{
  "pluginId": "amplify-nodejs-function-runtime-provider",
  "functionRuntime": "nodejs",
  "useLegacyBuild": true,
  "defaultEditorFile": "src\\index.js",
  "scripts": {
    "build": "npm.cmd install --no-bin-links --production"
  }
}

Whereas other functions had this:

{
  "pluginId": "amplify-nodejs-function-runtime-provider",
  "functionRuntime": "nodejs",
  "useLegacyBuild": true,
  "defaultEditorFile": "src/index.js"
}

the other 2 working functions are triggers built from Post Confirm and Post Auth during >amplify add auth , but the failing one was just an >amplify add function, and was not in use, I used >amplify remove function, and the error was gone.
So there is something wrong with the amplify add function???

[qwikag]

@ykethan,
not sure if my above comment helps.
but these functions I built were only in the last week.
custom failed Auth triggered were ok.

[josefaidt]

Closing as this issue is now resolved with the release of CLI 12.6.0

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.