-
-
Update the explore-related components to be compatible with react-router v6 according to this checklist:
- [ ] Stop using route props and rely on `useParams()` instead
- [ ] Use `useNavigate()` in…
-
## React Router Dom
```
yarn add react-router-dom
```
## 사용 방법
1. `` 를 사용하던가
2. `createBrowserRouter` 를 사용하던가
### BrowserRouter
- index.tsx -> App.tsx -> Main.tsx 순으로 참조하고, PageHeader.tsx …
-
Update the plugin-related components to be compatible with react-router v6 according to this checklist:
- [ ] Stop using route props and rely on `useParams()` instead
- [ ] Use `useNavigate()` ins…
-
-
# Bug Report
- [x] I’ve searched for any related issues and avoided creating a duplicate issue.
## What happened
Using a `va-link` component, I do not see a way to trigger a react routing eve…
-
### Versions
- vite-plugin-federation: 1.2.3
- vite: 4.2.1
### Reproduction
Host and remote apps are using react-router-dom for nested routing. Separatelly, applications are working corr…
-
-
react-router: allow for easier query params (for reports)
Use hash router - so that routing works with IPFS deployment (Katty will check with Onno)
-