Using hash history instead of browser history?

On previous versions we were able to pass a hash history to the connectRoutes function, like:

const history = createHashHistory()

export const {reducer, middleware, enhancer} = connectRoutes(
  history,
  routesMap,
  options
)

It seems like now, with history handled internally, there is no way to use hash history anymore, is that correct and intended?

[faceyspacey]

Thanks for pointing this out.

There is now a createHistory option which you can pass the hash history to or your own fork/implementation etc. Eg:

import createHashHistory from 'history/createHashHistory'

connectRoutes(routesMap, { createHistory: createHashHistory })

Otherwise, for anyone reading this, if you’re not passing your own createHistory factory, RFR will automatically pick the memory or browser history automatically for you based on the environment it detects. I.e. on the server or React Native it will pick createMemoryHistory and if in the browser it will pick createBrowserHistory 😃

[chanand]

@faceyspacey I’m using the hash history because I’m deploying a single page app (with no SSR) while I have no control on the hosting server.