I had been doing that, and not getting to where I needed to be.
However, I’ve just looked more carefully at the instruction to use ‘scoop update nodejs-lts’ to install new version. (I had misread nodejs-lts as nodejs=-is, and of course that wasn’t going to work . . .
I spelled things correcter and it updated me to nodejs-lts from v20.9.0 to v 20.10.0, and I’m seeing from the Node.js team article from today that it is the most current version for NodeJS (LTS), so I guess I’m good and just a wee bit smarter about Wappler than I was a few hours ago.
Thanks for the leg-up!
I’m learning that the current-current version is Node.js 21.2.0 (release date 2023-11-14. So that’s newer . . . but also that the LTS that trails the version number means “long-term support” which generally means that critical bugs have been fixed for at least 30 months.
Would I be correct in understanding that if I were to do the install from scoop without tagging the -lts to the nodejs that it would be possible for me to install the most current version . . . with the caveat that I might be flying loose-as-a-goose with respect to mangling my work with a bug that sinks its fangs into my code?
I am still on Node v 20.7.0 without a problem. But if you want to update, be careful of the latest version as this may contain bugs. LTS is the better option.