Modern JS features about abstract-state-router

[saibotsivad]

You could take a proverbial page from a solid project like moment.js and write everything in ECMAScript6, but still provide a transpiled ECMAScript5 JS file to maintain backwards compatibility/be friendly.

Copied from their README file:

Moment 2.10.0 does not bring any new features, but the code is now written in
ECMAScript 6 modules and placed inside src/. Previously moment.js, locale/*.js and
test/moment/*.js, test/locale/*.js contained the source of the project. Now
the source is in src/, temporary build (ECMAScript 5) files are placed under
build/umd/ (for running tests during development), and the moment.js and
locale/*.js files are updated only on release.

If you think about going this route, I suggest looking at how they structured their files. You probably wouldn't need that much complexity, but they really do try to handle lots of edge cases, so it's a useful exercise.

[TehShrike]

I've updated the current post based on my current thought process.

Modernizing the internal code and dropping the Promise polyfill doesn't mean that the interface needs to change, or that I need to stop shipping ES5 code.

Any breaking changes will be pushed off into some-day eventually dream-land (which will still hopefully not be too disruptive).

[TehShrike]

This was fixed in #115

[TehShrike]

It would be a good idea to resolve #86 before this.

[TehShrike]

That's a valid path, but moment.js is different from abstract-state-router in that it has always aimed to support the "download a single file and include it with a <script> tag" crowd, and abstract-state-router has always only aimed to serve the CommonJS-transpiling crowd.

Narrowing my audience like this makes me feel all right about using modern features with a browser property in the package.json for browserify, while assuming that the Webpack folks already have ES6->ES5 transpiling turned on if they care about supporting ES5.

It would be nice to maintain wzrd.in support via transforms, though.