package.json missing "engine" property about superlogin

[colinskow]

OK I will definitely do that for the next release, which I hope to get working on in the next few days. I will go over all the pending pull requests and issues.

I'm relatively new to Javascript and this is my first major open source project, so thanks for all your help!

[tohagan]

Thanks Colin ... This will really help me to know what node engines to do testing with and for new projects based on this lib .. What engine to select for my projects.

[tohagan]

Oh yeah ... If possible (and your dependencies support it!) would be great to use the 4.3.x as they are LTS (long term support).

• https://nodejs.org/en/blog/release/v4.3.0/
• https://github.com/nodejs/LTS

https://nodejs.org/en/blog/vulnerability/february-2016-security-releases/ - reports that there will be no further 4.2.x LTS releases (now LTS is 4.3.x).

[colinskow]

Yes, I do my personal testing on 4.x. I believe it will also run on 5.x
without a problem. I will add 4.x to package.json next release.
On Mar 14, 2016 7:30 AM, "Tony OHagan" [email protected] wrote:

Oh yeah ... If possible (and your dependencies support it!) would be great
to use the Node 4.2.x or 4.3.x as they are LTS (long term support).

https://nodejs.org/en/blog/release/v4.3.0/

—
Reply to this email directly or view it on GitHub
#39 (comment)
.

[colinskow]

Official NPM documentation specifies "engines" as the correct field.

I am going to add this:

"engines" : {
    "node" : ">=4.0.0"
  }

It should work on both LTS and latest version, and be tested against both.