Out of date engines field in package.json

[devramsean0]

Hi!
I’m trying to implement actio as the API server For a new project.
However, yarn won’t let me install it if I’m running a node.js version later than 16.
This is a dealbreaker for me as node 16 is now seriously out of date.

Is there a reason why the package field is so out of date and so inflexible? Or has nobody updated it yet?

[crufter]

Hi @devramsean0,

It is an oversight on my part as Actio is lifted out of a project that used some dependencies only working with older node versions (or something like that - tbh I'm not hugely into Node and I thought it's a minimum version and not an exact one?).

Let me try to upgrade it quickly

[crufter]

Can you try installing 0.3.5 please?