Stale values when navigating from within a boundary
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 20.8k
- Forks
- 2.3k
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 156
Description
Describe the bug
When navigating from within a boundary the route sees stale values.
Reproduction
- Click Go
- You should see
1, you will seeUncaught TypeError: can't access property "y", (intermediate value).x is undefinedin the console.
Switching to {#await block does work every time, await tick() does not help, flushSync does not help, setTimeout helps.
If it does not reproduce, try to refresh with the Refresh button on the main route, it's quite inconsistent in the repro but you can hit it.
Logs
Uncaught TypeError: can't access property "y", (intermediate value).x is undefined
System Info
N/A
Severity
annoyance
Additional Information
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by running the linked SvelteLab reproduction and follow the navigation triggered by clicking Go from within the boundary. Compare the failing behavior with the working {#await} block, noting that tick() and flushSync() do not help while setTimeout() does; done means the route consistently shows 1 without the TypeError.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend, web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100