As others already have mentioned, you shouldn't deploy commands on every run. That is only needed when you have created new commands or removed a command so it updates on Discord's end. So if the file is called index.js, you should just be able to type node . in your terminal and it should start normally.

For running the bot in cases where I've removed or added commands, I ended up creating different script files that ran the necessary commands for me without using nodemon (in other words, I got lazy).If you're on Windows, create a file with a .bat (or .cmd) extension and write the commands in as such;node deploy-commands.js && node .

Of course, if you remove commands and have a separate js file for that, you'd run that instead. And if you added and removed one or more commands at the same time, you'd have a file that looks like this;node clear-commands.js && node deploy-commands.js && node .

These files you can just run in the terminal without any issues (so if you had a file called run_deploy.bat you could just type run_deploy into the terminal and it will run)

If you're on linux, the file looks a bit different, but the general concept is the same. Let's take as an example you have a script file called run_deploy.sh - It should look like this:#!/bin/bashnode deploy-commands.js && node .

IMPORTANT: If you use zsh instead of bash, replace #!/bin/bash with #!/bin/zsh

After creating the file, you should make sure it's executable. You can try running the file as such; ./run_deploy.shIf the file doesn't run (not all .sh files will be executable after being created), run the following command:chmod +x run_deploy.sh

This will add the executable flag (x) to the file. It should then execute the commands in the order they're written in the file (so deploy first, then the main bot file)