You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm relatively new to React; apologies if this is a really naive question.
What are the technical advantages to createHistory that make it preferable over hashHistory? For example, is there a major performance/efficiency boost from it using the History API?
The docs state that browserHistory is recommended, even though this comes at the cost of the additional server config and needing to hard-code or configure your base URL for different servers via basename.
hashHistory "just works", however, regardless of the base URL from which the files are served. No server config needed. Bundle your app, host it from any URL/path on a server, good to go.
It might be good if the docs went a bit further in explaining why it browserHistory is recommended even though it involves more complexity.
The text was updated successfully, but these errors were encountered:
We want to make sure that the GitHub issue tracker remains the best place to track bug reports and feature requests that affect the development of React Router.
We also have an active and helpful React Router community on Reactiflux, which is a great place to get fast help with React Router and with the rest of the React ecosystem. You can join at https://discord.gg/0ZcbPKXt5bYaNQ46.
I'm relatively new to React; apologies if this is a really naive question.
What are the technical advantages to
createHistory
that make it preferable overhashHistory
? For example, is there a major performance/efficiency boost from it using the History API?The docs state that
browserHistory
is recommended, even though this comes at the cost of the additional server config and needing to hard-code or configure your base URL for different servers via basename.hashHistory
"just works", however, regardless of the base URL from which the files are served. No server config needed. Bundle your app, host it from any URL/path on a server, good to go.It might be good if the docs went a bit further in explaining why it
browserHistory
is recommended even though it involves more complexity.The text was updated successfully, but these errors were encountered: