-
Notifications
You must be signed in to change notification settings - Fork 10.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bypass react router path matching #222
Labels
help wanted
Issue with a clear description that the community can help with.
Milestone
Comments
This will be cleaner with remix-run/react-router#3262. |
As of React Router v2.2.0, |
This is great! Thanks! |
KyleAMathews
added
help wanted
Issue with a clear description that the community can help with.
Hacktoberfest
labels
Oct 12, 2016
Closing as very old |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I discovered recently that react-router can be very slow at matching routes remix-run/react-router#3215
This will soon be (mostly) fixed but there'll still be 10-15 milliseconds spent matching the router (that's on a 2015 MBP so much much slower on an old android) that we should avoid.
We can load our own routing table into the browser and match path changes against that which will drop path matching times down to microseconds.
This will also probably make code splitting more convenient #10
The text was updated successfully, but these errors were encountered: