distributions VS Nodemon.io

The npx install playwright install when run inside the official docker container installs node 18 version. Since last few weeks node 18/20 installation is failing on few Linux distributions - nodesource/distributions#issues/1576.

Hello guys! I want to say first that this problem is caused by me. So I kind of know when it append. I will try to explain what's my problem. Basically, any time I try to install with apt or deb packages, there is an error. This happend after I installed node js with https://github.com/nodesource/distributions. Now every time that I install something it fails. The other problem for me is that i'm not english and my os is in french. The thing is, i can't juste copy/paste the errors because there's no result in Google. I tried to find a way to get the error message in english but it did not worked. I'm not used to it but I would like help. So If anyone knows what the problem could be this would be incredible. Thanks!

Node will be the next step, using setup code made from this open-source repository (can also choose a different version of Node/npm):

This is now fixed: https://github.com/nodesource/distributions/issues/1507#issu...

Lets now install npm and Node.js which we are definitely going to need for installing JavaScript packages. You can find the latest versions of Node.js here https://github.com/nodesource/distributions/blob/master/README.md

The NodeSource Node.js distributions repository contains information both about supported versions of Node.js and supported Linux distributions. To learn more about usage, see the repository: https://github.com/nodesource/distributions

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.