Setting package.json nodejs version gets overwritten

[NGM]

I tried again and double checked both project files stated the same >=18 but still get 16.20.2 when checking heroku version.

@George - any thoughts?

[Teodor]

This is now improved in Wappler 7 beta 13

[hs-rene]

Awesome thank you!!

[NGM]

Many thanks, will do some testing later and report back.

[NGM]

Im guessing Im doing something wrong because:
I updated the package.json file to be
"node": ">=18",

then deployed the release and still got the same version information:

C:\Users\nmund\OneDrive\Documents\Work\EnienApp2>heroku version
heroku/9.5.0 win32-x64 node-v16.20.2

Help please,

Nigel

[George]

Heroku seems to have a different notation and not supporting the >= try entering just:

20.x