npm run deploy failure - npm

Question

This is a followup to my previous post -> Contract method is not found I am now attempting to pass npm run deploy however, it seems to be failing with the following.
//helper.testnet.near.org, file: ./out/main.wasm
An error occured
Error: ENOENT: no such file or directory, open './out/main.wasm'
at Object.openSync (fs.js:476:3)
at Object.readFileSync (fs.js:377:35)
at exports.deploy (/Users/User_Name/Desktop/nearTest/testVote/node_modules/near-cli/index.js:42:49)
at processTicksAndRejections (internal/process/task_queues.js:93:5)
at async Object.handler (/Users/User_Name/Desktop/nearTest/testVote/node_modules/near-cli/utils/exit-on-error.js:39:9) {
[stack]: "Error: ENOENT: no such file or directory, open './out/main.wasm'\n" +
' at Object.openSync (fs.js:476:3)\n' +
' at Object.readFileSync (fs.js:377:35)\n' +
' at exports.deploy (/Users/User_Name/Desktop/nearTest/testVote/node_modules/near-cli/index.js:42:49)\n' +
' at processTicksAndRejections (internal/process/task_queues.js:93:5)\n' +
' at async Object.handler (/Users/User_Name/Desktop/nearTest/testVote/node_modules/near-cli/utils/exit-on-error.js:39:9)',
[message]: "ENOENT: no such file or directory, open './out/main.wasm'",
errno: -2,
syscall: 'open',
code: 'ENOENT',
path: './out/main.wasm'
}```

Answer 1

If you are using create-near-app it expects, as this error suggests, that the generated binary be located at ./out/main.wasm. Currently there is a script, compile, and it creates a symbolic link from the binary to out/main.wasm, which either the debug or release. The following line in the script is hard coded to expect the name greeter.wasm.
`./build/${debug ? 'debug' : 'release'}/greeter.wasm`
So my guess is if you have renamed the project and it is silently failing. Until we fix this issue, try changing the above to the name of the generated wasm file.