Add support a new SvelteKit routing system
See original GitHub issueWe have no load function in layout.svelte
anymore, and an alternative like +layout.js
is not working automatically because SvelteKit can call it after +page.js
.
We can still use it if we will call directly await parent();
in each +page.js
but looks like a hack, add extra boilerplate and reduce performance.
I suppose we should find a better place to init i18n and it shouldn’t depend on the order of +layout.js
and +page.js
.
Issue Analytics
- State:
- Created a year ago
- Comments:15 (6 by maintainers)
Top Results From Across the Web
Routing • Docs • SvelteKit
Routing. Edit this page on GitHub. At the heart of SvelteKit is a filesystem-based router. The routes of your app — i.e. the...
Read more >Introduction • Docs • SvelteKit
You don't need to know Svelte to understand the rest of this guide, but it will help. In short, it's a UI framework...
Read more >SvelteKit • Web development, streamlined
Add service workers for offline support. Generate AMP-compliant pages if you really have to. Build complex UIs with unusually powerful filesystem-based routes.
Read more >Advanced routing • Docs • SvelteKit
You can ensure that route parameters are well-formed by adding a matcher — which takes the parameter string ( "3" or "potato" )...
Read more >Configuration • Docs • SvelteKit
When pages are prerendered, the CSP header is added via a <meta http-equiv> tag (note that ... the files that define the structure...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I wish there was some wait of setting up a reproduction that allows to consistently reproduce this locally so it can be fixed.
@stalkerg could you please provide a little more context on how to implement it?