Roadmap & Features

Stage 1

• Use original source and add/update build system
• Convert source over to Typescript.
• Automated tests: especially useful for Pull Requests (Jasmine?, Mocha?)
• API Documentation within code (TypeDoc? GitBook?)

Stage 2

• Fix / close all valid open issues
• Merge / add / close all open Pull Requests

Note

This is an open issue so people can discuss and put their own views in for getting things moving again - not for bug reports and feature requests which should be opened as separate issues - if you want to refer to an already open issue then feel free, but we do want to try to get them all closed / resolved as soon as possible anyway.

---

• Typescript is described as “Javascript with types” - the code is pretty much identical but has type annotations added, so var test = "abc"; test = 123; doesn’t give a warning in Javascript, but would in Typescript as you’re trying to change the type of it (nice at preventing errors) - you could also use var test: string; test = "abc"; test = 123; to get the same warning.

[ydaniv]

But then the source would NOT be in JavaScript. And that is bad. Very bad. Please don’t do that. It’s a bad practice to write the source of a public open-source library in a an opinionated dialect of language.

[ydaniv]

@kenwheeler regarding wins from converting to es2015: it’s not a must, but if possible, moving on with the world and having the source written in the most up-to-date version of the language is good practice. Personally, I still didn’t find the time to convert anything I own/maintain to es2015.

@Rycochet I’d say drop all the oldies! Especially IE, which you can support now at 11. The problem now is old Androids, and question is whether to support below 4. Same for iOS below 7.1.

@Joeao agreed!