Cutting releases v1.9 and v2

Hey @mjackson 👋

tl;dr

• I think master is ready to be published as 1.9.
• Could you please review the changes in next?
• If you’ve given your 👍 for next, I’ll go and polish the docs

A bit of an update on the current state of the repo. I’ve merged most of the outstanding PRs into either master or next. I think master should be publishable as a minor version bump, as we’ve only added Typescript definitions (#76) and the onChange callback (#95). Docs look good, and I’ve prepared the CHANGES.md, you just have to add the release date.

I don’t think next is ready for deployment yet, as I’d like to do a cleanup of the docs. We’ve accumulated some new features over time, and while they’ve been added to the docs, I feel the docs now lack cohesion. Moreover, there’s an outstanding PR which should improve the state of SSR (mainly preventing nasty edge-case bugs).

After we complete those things on next, we could release a v2-alpha. What do you think?

[gersomvg]

A minor version bump shouldn’t be too much work right? Would be nice to have the Safari event listener bug solved, which is merged a month ago, @mjackson .

[edorivai]

@flq I have not created a fork - if that is what you mean. As it stands releases are done by @mjackson, who’s a busy man 😅. I guess you could fork this repo for yourself if you really have to. Otherwise, if the TS typings are all you’re after, you can just copy/paste them into your own repo, or you could even create an entry in DefinitelyTyped if you feel like it.