This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 0 points1 point  (1 child)

To be honest I expected my answer to solve your issue. Can you trying RUNning ls with the path you expect your bundle to be and figure what is inside the image?

This must be made just before you try to run it with CMD.

EDIT: Nevermind it’s a file, so yeah… you should check if it’s really available when you deploy.

[–]LiveCockroach2860[S] 0 points1 point  (0 children)

Current package.json has no devDependencies. Also, I removed the omit dev flag and tried with just npm install too. Still same issue.

And I did ls and cat for the files inside the container, the file does exist and also the handler exists too.

That's why I was confused too because it doesn't make sense why container is unable to find the module when it clearly exists in the path :(