Node versions to support

[mblarsen]

1. Should we follow Node LTS?
2. Should we update frequently
3. Does anyone use oooold node versions?

[Santinell]

1. As for me, I use only LTS. (maybe we can keep one outdated version like 8.x now)
2. If we follow Node.js plan you can update it once a year
3. ...

[mblarsen]

I was also thinking to follow whatever Mongoose is following.

[AlbertHambardzumyan]

Looks like mongoose still supports Node.js v4, see.

This package is always integrated with mongoose and at first glance following whatever Mongoose is following makes sense. However, Node.js v4 eol was in 2018-04-30 and if someone is running production code on v4 then they definitely should consider upgrading it.

As for me, we should follow Node.js release schedule and support >=10 for today

Also, let's consider

• adding engines in package.json
• build with Node.js >10 too, see travis config

[mblarsen]

Good points @AlbertHambardzumyan

This package is always integrated with mongoose and at first glance following whatever Mongoose is following makes sense. However, Node.js v4 eol was in 2018-04-30 and if someone is running production code on v4 then they definitely should consider upgrading it.

Yeah and secondly they probably wont go back and add this plugin.

I'm leaning to @Santinell's suggestion of one outdated version of LTS and then tagging being clear in the changelog when a shift happens.

[AlbertHambardzumyan]

❤️