You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the Directus project restricts compatibility to Node.js version 18, specifically version 18.17 or higher. However, considering Node.js version 20 is also in Long-Term Support (LTS) and compatible with the project's requirements, it's imperative to update the project configuration to allow Node.js version 20.
By making this tiny tweak, users will be able to utilize the latest LTS version of Node.js seamlessly with the Directus project, ensuring enhanced performance and stability while aligning with the latest standards of the Node.js ecosystem.
The text was updated successfully, but these errors were encountered:
Leaving this one open for now as i dont think there is an explicit ticket for this. But yes we are aware and have been working towards fully supporting node 20 for a while.
Not a tiny tweak. We already know isolated-vm doesn't "just work" the way you'd expect on Node 20, so we might have to update a couple things there or make sure we update the docs to warn people about the additional Node flags required to run it.
@cenfun It supports node 20, but it requires a node flag to be set to run. The hope was that flag would become optional over time but it seems like that's not the case.
Describe the Improvement
Currently, the Directus project restricts compatibility to Node.js version 18, specifically version 18.17 or higher. However, considering Node.js version 20 is also in Long-Term Support (LTS) and compatible with the project's requirements, it's imperative to update the project configuration to allow Node.js version 20.
By making this tiny tweak, users will be able to utilize the latest LTS version of Node.js seamlessly with the Directus project, ensuring enhanced performance and stability while aligning with the latest standards of the Node.js ecosystem.
The text was updated successfully, but these errors were encountered: