Don't use ES6 but vanilla JavaScript for this

[iduuck]

This is such a lightweight script. Why should it utilize ES6 over the good'ol vanilla javascript (ES5). When using the latter it's unnecessary to compile it and the gulpfile is not necessary (perhaps for multi-system compatibility such as support for Require.js, System.js and other module loaders).

What do you think?

[iduuck]

Another thing that should make the point: Size!

I just cloned your repo and the unminified script has a size of 2.4k. The compiled (es6) script has 1.2k and the vanilla js minified would have a total of 927b. This would be a good point.

2.4K  =  jump.es6.js
1.2K  =  jump.js
927B  =  jump.min.js

[callmecavs]

@iduuck i see where you're coming from, but honestly to save 1 kb I'd rather use the latest spec, support more complex build processes (Common JS, AMD, etc), and somewhat "future proof" the library. nonetheless, I appreciate your efforts in providing the file size comparison.

[julkue]

@callmecavs The docs still say:

Jump was developed with a modern JavaScript workflow in mind. To use it, it's recommended you have a build system in place that can transpile ES6, and bundle modules. For a minimal boilerplate that fulfills those requirements, check out outset.

However, at least the npm package is shipped with already transpiled files.