Gerben

> Would it be enough to URL-encode the type? Unfortunately, no. That would also percent-encode characters of the media type that we should keep intact, such as the slash and...

Thanks for reporting. This happens indeed because calling highlightRange may make the given range unusable (because we modify the nodes that range points to). Before version 3 of highlight-range, it...

> I’d been avoiding ES2015, such as arrow functions, because it looks like you’d stuck to ES5. Is ES5 a goal? Oh yes I forgot this module is plain ES5,...

This is a valid desire indeed, thanks for picking it up! I have had a similar intention to give this module more flexibility some day. I would actually have no...

Sure. I am happy to first make a v1.1 that is backwards compatible, then leave the other API ideas for later. Tests would be most welcome anyhow.

Thanks for the suggestion. The use case seems completely valid, you may want to know when all URL parameter changes have been handled. Our current approach is lacking, as it...

So.. sounds like either solution would work for you? I am still poised towards the bulk hander approach, especially as it may also enable many other types of customisation. I...

> Hi @Treora, are there any new on this? No news; I have not touched this module in ages as I have not worked on any redux-based projects, and have...

> I was under the impression that omitting `replaceState` from the options would allow the user to cycle back through the selections they made using the back button That should...

Glad you like it! This module could be modified to allow passing a replaceState option for individual params that would override the ‘global’ replaceState option. It would need some changes...