Hi, I am building a library for Node.js. It's an alpha stage, no intro, docs, work in progress: https://github.com/witoldsz/micro-message-hub.node
Right now I am developing on engine version 4.x, using Babel for features like destructing assignment, default parameters, ES2015 modules, etc. Now, when Node v.6 is out, the source code could be left almost as-is, maybe with the exceptions of ES2015 modules. There are also older engines which might be still used by some. The question is how would you target several engine versions by your lib? Should I fork it, adjust package.json, .babelrc, build and release as a new packages? That seems like a tedious job... Or I could create branches and maintain all the tiny differences and publish as same package with some prefixes in version numbers? It would break the semantic versioning I guess, and it still does not seem to be fun. What do you say? -- Job board: http://jobs.nodejs.org/ New group rules: https://gist.github.com/othiym23/9886289#file-moderation-policy-md Old group rules: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+unsubscr...@googlegroups.com. To post to this group, send email to nodejs@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/nodejs/CAAWTntgswxVTi6aA2OrxY6nVtAFhxax5Vk8_KFRzcawro959hw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
