Convert code to ES6 and add a transpile build step

[BehindTheMath]

As mentioned here, I think this should wait until we finish fixing all the existing issues, so we don't cause any conflicts.

[robinnorth]

This sounds sensible, if this still ends up using Browserify with the addition of the Babelify transform, you could add the following topackage.json to allow people bundling the npm package through Browserify (my usage) to get transpiled output as well (Browserify won't transform anything under node_modules by default):

{
  "browserify": {
    "transform": ["babelify"]
  }
}

[MoOx]

Another possibility is to include in npm package compiled files (but ignore those in git).

[phifa]

Webpack?

[BehindTheMath]

@phifa I believe Webpack is overkill for a library like Pjax. Webpack is more suited for a webapp with different types of assets or multiple entry points. For Pjax, Babel and Browserify should be fine.

[MoOx]

Rollup should be a good candidate.

[BehindTheMath]

Do we even need Rollup?

[MoOx]

I just know that Rollup is nice for library authors

[BehindTheMath]

True. I'll have to look into the differences between Rollup and Browserify.

[BehindTheMath]

@MoOx What browserlist settings do you think we should use for Babel?

[MoOx]

No idea what is best to use. Keep defaults?