Type Error : cmd is not a function
jaison-jj
TRIALOP

2 years ago

When I initiated a redeployment on the railway, the build was successful, but the server did not start, and the application did not respond. When I rolled back the process, it worked fine. This issue also occurs when pushing changes.

I noticed on the deployment log that the "TypeError: cmd command was not found"

#12 16.51 medusa start

#12 16.51

#12 16.51 Start development server.

#12 16.51

#12 16.51 Options:

#12 16.51 --verbose Turn on verbose output [boolean] [default: false]

#12 16.51 --no-color, --no-colors Turn off the color in output [boolean] [default: false]

#12 16.51 --json Turn on the JSON logger [boolean] [default: false]

#12 16.51 -H, --host Set host. Defaults to localhost [string] [default: "localhost"]

#12 16.51 -p, --port Set port. Defaults to 9000 [string] [default: "9000"]

#12 16.51 -h, --help Show help [boolean]

#12 16.51 -v, --version Show the version of the Medusa CLI and the Medusa package in the current project [boolean]

#12 16.52 TypeError: cmd is not a function

#12 16.52 at /app/node_modules/@medusajs/medusa-cli/dist/create-cli.js:198:13

#12 16.52 at /app/node_modules/@medusajs/medusa-cli/dist/create-cli.js:48:30

#12 16.52 at Object.handler (/app/node_modules/@medusajs/medusa-cli/dist/create-cli.js:16:21)

#12 16.52 at Object.runCommand (/app/node_modules/yargs/build/lib/command.js:196:48)

#12 16.52 at Object.parseArgs [as _parseArgs] (/app/node_modules/yargs/build/lib/yargs.js:1043:55)

#12 16.52 at Object.parse (/app/node_modules/yargs/build/lib/yargs.js:584:29)

#12 16.52 at exports.default (/app/node_modules/@medusajs/medusa-cli/dist/create-cli.js:353:10)

#12 16.52 at Object. (/app/node_modules/@medusajs/medusa-cli/dist/index.js:38:26)

#12 16.52 at Module._compile (node:internal/modules/cjs/loader:1369:14)

#12 16.52 at Module._extensions..js (node:internal/modules/cjs/loader:1427:10)

2 Replies

jaison-jj
TRIALOP

2 years ago

I found this in the deployment logs.

Attachments


facundocapua
HOBBY

2 years ago

I'm getting the exact same issue, please advice on this.


Welcome!

Sign in to your Railway account to join the conversation.

Loading...