discord.js VS Nodemon.io

Now that you've installed Node.js and know how to open your console and run commands, you can finally install discord.js!

We're beyond excited to unveil RoboPlay! It's not just another hosting service; it's a next-gen platform tailored for Discord.js bots, especially those powered by the Robo.js framework.

Context: Robo.js is a framework designed for creating Discord.js bots with ease and best practices by default. Plugins extend your bot's features right away!

Note the video is 2 years old. Discord.JS is constantly changing alongside the Discord API. This is why you should follow official and up to date guides and not just copy paste off of youtube: https://discord.js.org/

The feature is not yet supported, but you can check the pull request for the feature here

Well, I recommend you JavaScript, it is good for beginners and there's a lot of content on internet. Once you understand and practice the basics, you can use discord.js to write your bots. They have a guide website if you are interested.

You can (with some effort) create your own bot using a library like Discord.js to use webhooks easier.

I want to dive into discord bot things but I was confused when I saw 2 sites of discordjs. There is https://discord.js.org/ and https://old.discordjs.dev/#/. Is the old one is no more supported? Which one to use? I couldn't understand the difference between them.

The GitHub issue that someone raised in the library can be found here: https://github.com/discordjs/discord.js/issues/9185

nodemon - enables automatic reload of your server after code change docs

Then, install nodemon (in the VSCode terminal also), which, to my understanding, automatically refreshes the server you'll be sending requests to, whenever you make a change. Using plain node.js, you'd have to manually stop and restart the server after every change.

That's already pretty good, but as you already know it's a PITA to work with this during development. You will have to rebuild your Docker images whenever you change your code, even though your apps will probably support hot-reloading out of the box (or with something like Nodemon if not).

Are you moving your projects to use ES Modules but you are facing some unexpected issues? You are not alone in this fight. In this tutorial, you will learn how to set up nodemon along with ts-node.

We can now use npm run dev to start the server using nodemon, which enables hot refreshing on changes.

Welcome to my blog, where we dive into the intriguing world of Node.js development and tackle one of the common stumbling blocks many developers encounter: the "Nodemon Error - nodemon.ps1 cannot be loaded because running scripts is disabled on this system." If you've ever come across this error while working with Nodemon, fear not! In this article, we will explore the causes behind this issue, understand why scripts are disabled on certain systems and most importantly, provide you with practical solutions to overcome this obstacle and keep your development workflow seamless. So, let's embark on this troubleshooting journey together and empower ourselves to conquer the Nodemon Error!

You’ll need to restart the server using node index.js whenever you change any project file. You can also use Nodemon to automate this.

nodemon will be required to monitor for any changes in our source code and automatically restart our server.