John Hoffer

I'm not a maintainer, but `HashRouter` is still [supported](https://reactrouter.com/en/main/router-components/hash-router) in v6.3.0. The beginning of the URL hash must be `#/`, since `hashType="noslash"` has [been removed in V5](https://github.com/remix-run/history/issues/912).

As it stands now, I'm [currently using this solution](https://github.com/thejohnhoffer/history/tree/publish-noslash#history-noslash) with a fork of `history`. UPDATE: I'm currently using [`use-hash-history`](https://yarnpkg.com/package/use-hash-history) as a stand-in for this PR, [following this template](https://github.com/thejohnhoffer/test-history-router#history-router-test-template). It should...

@chaance Thank you for taking a look at this PR. Apologies for the sudden influx of code additions. To make testing my changes easier, I have created a new workspace...

> According to the tests, this is a non-breaking change with added support of `hashRoot: ""` as a replacement for the lost feature of `hashType: "noslash"`. For my purposes, this...

Hi @chaance -- I've again tested that the new and old tests all pass. My own alternative to this PR, [use-hash-history](https://github.com/thejohnhoffer/use-hash-history), has a few users. I'm happy to continue maintaining...

I have waited on the merger of PR #911 for a while. As a workaround, I have created [use-hash-history](https://www.npmjs.com/package/use-hash-history), which provides a Proxy around `history` [in

It seems this issue may go unaddressed because [this rejected issue](https://github.com/remix-run/react-router/issues/7703) is not a concern for [react-router](https://github.com/remix-run/react-router). It seems `history` exists primarily to serve React Router, [according to](https://github.com/remix-run/history/issues/810#issuecomment-825978388) @mjackson: >...

With `[email protected]`, the parameter proposed for `createHashHistory` can take effect immediately, thanks to the [prematurely released](https://github.com/remix-run/react-router/releases/tag/v6.1.1) (as of now unstable) `HistoryRouter` API. So, if PR #911 were released with `history@next`,...

@chaance do you see value in this feature? PR #911 has been ready to solve this for some time now.

It seems [that this line in geotiff.js](https://github.com/geotiffjs/geotiff.js/blob/b4e64639708940cac15c435e99b918e1771b083b/src/geotiffimage.js#L495) runs (for every pixel in the loaded block!) DataView.[getUint8][u8] (or [getUint16][u16], etc) to extract single pixels. I believe it may be more efficient...