watchexec VS fnm

Hi, I am using Watchexec (https://github.com/watchexec/watchexec/releases) to monitor folder changes, but I want to exclude some folders. What parameter should I use to perform the route exclusions?

Use https://github.com/watchexec/watchexec

There's something similar to this called watchexec, which you can have a look at https://github.com/watchexec/watchexec

Or use watchexec which will do 95% of what you need and you're not tied to nodejs.

watchexec

I use watchexec to automatically run the code when saved, you should customise this to your liking.

OTOH PowerShell will not keep watching and is one of the requirements. In the past I've successfully used watchexecrepo and inotifywaitrepo.

I prefer watchexec as it's cross-platform.

Not specifically for frontend but a handy tool for quickly setting up auto-runners, auto-testers, auto-linters, auto-formattere etc etc. watchexec

Install nodejs: (I highly recommend using a node version manager like fnm) and to install a recent node version (current long term support is 16+)

I highly recommend setting up nodejs with a version manager, nvm was and still is a popular option, however, I now recommend and have been using fnm, a simpler and faster alternative to manage my nodejs versions.

I switched from nvm to fnm a few years ago and have never looked back. Zero performance issues and it supports .nvmrc files.

https://github.com/Schniz/fnm

Are you using some kind of node version manager like fnm?

If it's your terminal that's slow in general and not neovim specifically I found that switching from nvm to fnm for managing node significantly faster at starting up my shell. I don't know whether this is what your issue is but I thought I'd share it regardless. https://github.com/Schniz/fnm

fnm is a fast and simple Node.js version manager. It's really easy to use and is much faster than nvm.

As a macOS user, it boils my brain whenever I've to type in something like ~/Library/Application Support/org.rust-lang.Cargo/config.toml. macOS users have been begging CLI tools to support XDG variables on macOS too. Setting defaults is a strong indication to the community what should be the "preferred" locations. The defaults defined in your article will invariably lead to some authors saying that if that path is good enough for cargo, then it is good enough for their tool. Even the latest draft RFC acknowledges that macOS should use XDG variables too. I've written more about this here.

Install something like Fast Node Manager from https://github.com/Schniz/fnm and install your Node from there. I work in the software field and tend to use the LTS releases for the TypeScript/React projects I work on.

fnm!

You’ll need pnpm and Node.js installed on your machine + some tool for switching node versions (e.g. fnm or nvm will work fine);