Closed dazoot closed 3 years ago
Could this be because this project doesn't use a package-lock.json? Try removing package-lock.json and node_modules, then doing an npm install. I'm not sure what the reasoning is behind not committing package-lock, but it can lead to issues.
package-lock.json
is generated on each build.
On node: 12.14.0
zonemta starts OK. On older node: 10.24.0
i get the error.
Ah alright, if you're using some kind of pipeline where this isn't a problem, ignore me haha.
Does not seem to be directly related to mongo driver though, but some other dependencies introduced by the new driver.
Yeah, the mongo driver needed upgrade but it does not support older Nodejs versions. I’ll update the required engine version in packge.json, current one is not correct (should be 11 not 10)
Can we support at least node 10 ? It seems node 11 is not getting any security updates.
mongodb v4 module is quite a large change, it is not 100% backwards compatible and going back to v3 module would mean that it only delays adopting v4 which will eventually happen anyway. From the docs they require at least 12.9, I'm not sure what's the difference exactly. Additionally at one point ZoneMTA will start requiring Node v14 because that's the version needed to provided MTA-STS support via the mailauth module.
Fair enough. Upgrade it is :)
I did an upgrade to
3.2.0
and the server does not start: