Closed mrclay closed 3 months ago
As far as I can tell my general roadblock is static Qwik sites don't use SPA navigation, even if you use navigate()
, and that I'm trying to rebuild what was originally a React SPA with react-router-dom. I figured "I'll get Qwik to make a fast loading default for my base route then mutate when SPA nav happens." I may need to roll my own custom useRouter
for this use case.
This definitely looks like a bug. I presume this does work with the node adapter?
I've not tested the node adapter specifically. It works with npm run dev
. I can test the node adapter later.
Please do, thank you!
@mrclay Did you solve the problem?
Hello @mrclay. Please provide the missing information requested above.
Issues marked with STATUS-2: missing info
will be automatically closed if they have no activity within 14 days.
Thanks 🙏
Which component is affected?
Qwik City (routing)
Describe the bug
When trying to track location changes, the
useTask$
hook fails to re-fire the hook body if the project is built with the static adapter.Example component code:
In dev mode, this works, but after
npm run build
the code indist
does not re-call the useTask$ given function.Reproduction
https://stackblitz.com/edit/qwik-starter-oaexpi?file=src%2Froutes%2Findex.tsx
Steps to reproduce
View http://localhost:3000. When clicking the links, the state should update with the useLocation() value.
System Info
Additional Information
No response