provide es5 as main entry point, es6 as module entry point

[asfordmatt]

Fixes #105

Signed-off-by: Matt Chapman mpchapman@gmail.com

[coveralls]

Coverage remained the same at 100.0% when pulling 3975564 on asfordmatt:master into 6c5ac50 on jsonata-js:master.

[mattbaileyuk]

While I don't believe module is officially part of the npm spec for package.json it looks like it's getting enough use in the likes of Webpack and rollup to be worth including here to specify an ES6+ version.

However, I am a bit concerned about switching the default for main from the native ES6 code to the transpiled ES5 version, which was intentionally avoided when that version was introduced, but it might be time to revisit that. I'm mainly concerned about what that means for projects which import JSONata, in particular those like node-RED which use require('jsonata').

[mattbaileyuk]

Thinking about this more, I'm not as concerned about that change as I was previously, and think this would be good to have as I'm such other people picking this up for their front-end projects, whether they're using Webpack or otherwise, are likely to run into this.

[coveralls]

Coverage remained the same at 100.0% when pulling fd7af99 on asfordmatt:master into dd3fe66 on jsonata-js:master.