cdk deploy 💣 "Error: ENOENT: no such file or directory node_modules/.bin/extract-zi"

[phstc]

This project was deployable a few days ago. Now it's consistently failing at this deploy stage.

Any ideas on what it could be?

project-app:  start: Publishing a8f79ee7f4eb850a5d8f78057d81a3dc7385727c055d3b1339168910c5e7273b:current_account-current_region
node:internal/process/promises:288
            triggerUncaughtException(err, true /* fromPromise */);
            ^

[Error: ENOENT: no such file or directory, open '/Users/pablo/project/backend/cdk.out/asset.04240ea1c08096049a762ee2db8dcb44c278d1373f46518776680674cd231741/nodejs/node_modules/.bin/extract-zip'] {
  errno: -2,
  code: 'ENOENT',
  syscall: 'open',
  path: '/Users/pablo/project/backend/cdk.out/asset.04240ea1c08096049a762ee2db8dcb44c278d1373f46518776680674cd231741/nodejs/node_modules/.bin/extract-zip'
}

Node.js v18.12.1

CDK Version: 2.86.0

It seems the compilation is not copying any .js files into the cdk.out directory cdk.out/asset.04240ea1c08096049a762ee2db8dcb44c278d1373f46518776680674cd231741/nodejs/node_modules/ the ENOENT above is because a missing cli.js.

For any module. If I open the same folder on the root node_modules, I see the .js files.

Force copying node_modules "fixes" it

cp -rf node_modules/* /Users/pablo/project/backend/cdk.out/asset.04240ea1c08096049a762ee2db8dcb44c278d1373f46518776680674cd231741/nodejs/node_modules/ 

but then exceeds the bundle size.

[peterwoodworth]

What asset are you trying to upload, and what is your code?

[phstc]

Hi @peterwoodworth thanks for looking into this.

I'm sorry, I found the problem (the problem was me) and forgot to report back.

The issue was with a layer with node_modules (chrome on a lambda). I recently find . -name "*.js" -type f -delete then I fixed the main node_modules, but I forgot to fix the lambda layer one. These node_modules were clashing.

[peterwoodworth]

Great to hear, thanks!

[github-actions[bot]]

Hello! Reopening this discussion to make it searchable.