Closed tomjeatt closed 1 year ago
The latest updates on your projects. Learn more about Vercel for Git ↗︎
Name | Status | Preview | Comments | Updated (UTC) |
---|---|---|---|---|
interbtc-ui-interlay | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | Aug 18, 2023 2:50pm |
interbtc-ui-interlay-testnet | 🔄 Building (Inspect) | Visit Preview | Aug 18, 2023 2:50pm | |
interbtc-ui-kintsugi | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | Aug 18, 2023 2:50pm |
interbtc-ui-kintsugi-testnet | ✅ Ready (Inspect) | Visit Preview | 💬 Add feedback | Aug 18, 2023 2:50pm |
Running Lighthouse audit...
Closes #1518
Found a much quicker fix. Our implementation was using
<Redirect to={} from={} />
which was behaving inconsistently. Router v5 documenation suggests using a nested route:This has fixed the problem without needing to bump the version of React Router.