Upgrade Node.js to version 18+

[Jengro777]

Now the minimum version of Debian installed by default is already V18.x, and I hope the Node.js version of Redash can be updated.

[justinclift]

Hmmm, I kind of remember Arik saying 18 has problems. No idea of the details though. It might just be a dependency thing, so could become "not a problem" once we've upgraded things a bit.

Really not sure though.

[gaecoli]

Upgrading will not bring substantial effect, and may cause instability. Upgrading is not recommended for the time being.

[Jengro777]

When I was deploying on Vercel today, I encountered this issue. I think it is necessary to open this issue.

Error: Node.js version 16.x has reached End-of-Life. Deployments created on or after 2023-08-15 will fail to build. Please set "engines": { "node": "18.x" } in your `package.json` file to use Node.js 18.

[justinclift]

Ouch. 😦

[Jengro777]

The compatibility watershed for many libraries is Python 3.9. Currently, our backend code is built on Python 3.7, and I think it should be changed to Python 3.8 when appropriate. Our frontend code is built on Node.js 14.7.0, and I think we should start using Node.js 18, but this may require a transition to Node.js 16.

As long as most scenarios can run, I think the update is worth it. This way, we can fix the code at a higher point.

[justinclift]

Ugh. I'm not sure why libraries are dropping support for Python 3.8 when it's not End of Life yet, and won't be until the end of next year:

https://devguide.python.org/versions/

[Jengro777]

I mean to give up on Python 3.7 and switch to Python 3.8.

[justinclift]

Yeah, Python 3.7's official End of Life is in... 6 days. 😄

[konnectr]

There is such a repository from python 3.10 https://github.com/Dingolytics/redash-wild-server

[justinclift]

Cool. That's a very interesting repository @konnectr. 😄