+page.svelte should not load data from parent +page.server.ts
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
Lets say I have the following project structure:
If I navigate from the shop page to the product page and then back to the shop page, the product page gets the data from the shop load function before navigation to the shop page.
The product page should not get the load data from the shop page.
Reproduction
Logs
Navigating to shop page: shop {load: 'shop'}
Navigating to product page: shop {load: '[product]'}
product {load: '[product]'}
Navigating back to the shop page: product {load: 'shop'}
shop {load: 'shop'}
System Info
System:
OS: macOS 26.3
CPU: (12) arm64 Apple M2 Max
Memory: 380.69 MB / 32.00 GB
Shell: 5.9 - /bin/zsh
Binaries:
Node: 24.11.0 - /Users/frankherzog/.nvm/versions/node/v24.11.0/bin/node
npm: 11.10.0 - /Users/frankherzog/.nvm/versions/node/v24.11.0/bin/npm
Browsers:
Chrome: 145.0.7632.76
Firefox: 146.0.1
Firefox Developer Edition: 145.0
Safari: 26.3
npmPackages:
@sveltejs/adapter-node: ^5.5.2 => 5.5.3
@sveltejs/kit: ^2.50.2 => 2.53.0
@sveltejs/vite-plugin-svelte: ^6.2.4 => 6.2.4
svelte: ^5.51.0 => 5.53.3
vite: ^7.3.1 => 7.3.1
Severity
serious, but I can work around it
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 with the linked StackBlitz reproduction and inspect src/routes/shop/+page.server.ts alongside the logged navigation sequence. Verify the transition from the shop page to a product page and back, then confirm that the product page no longer receives the shop load data before navigation completes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100