I believe it uses something like the index of the item as the default when you do not provide a key. This can be validated by using {#each things as thing, index (index)} <Thing current={thing.color}/> {/each} which gives the same behavior as not using a key in the first place. Let’s call the <Thing> that … Read more
The above solutions won’t work. This is the new way: export async function load({ params, url }) { let lang = url.searchParams.get(‘lang’); let q = url.searchParams.get(‘q’); return { lang, q }; } Then, please reach it as this: import { page } from ‘$app/stores’; $page.data.q Thanks to Richard this is much better than acknowledging export … Read more
As of SvelteKit 1.0 the path should be a directory in brackets, e.g. for /blog/<slug> you will add the following: src/routes/blog/[slug] |_ +page.js |_ +page.svelte Then in src/routes/blog/[slug]/+page.js you can add something like export const load = ({ params }) => { return { slug: params.slug } } which will return it as a data … Read more
TL;DR Just wrap the handler function in another function. For elegancy, use the arrow function. You have to use a function declaration and then call the handler with arguments. The arrow function is elegant and is good for this scenario. Why do I need another function wrapper? If you would use just the handler and … Read more
Answering my own question thanks to Theo from SvelteKit Discord: Use $$app-navigation import { goto } from ‘$app/navigation’; function routeToPage(route: string, replaceState: boolean) { goto(`/${route}`, { replaceState }) } replaceState == true will replace the route instead of adding to the browser history. So, when you click back, you will not go back to the … Read more
The sveltejs/template uses sirv-cli. You can add –port or -p in your start:dev script in package.json. Instead of: “start:dev”: “sirv public –single –dev” Use: “start:dev”: “sirv public –single –dev –port 5555” You can see more of sirv-cli options: https://github.com/lukeed/sirv/tree/master/packages/sirv-cli
You can use {#each …}, like: {#each Array(3) as _, i} <li>{i + 1}</li> {/each}
TL;DR Just wrap the handler function in another function. For elegancy, use arrow function. You have to use a function declaration and then call the handler with arguments. Arrow function are elegant and good for this scenario. WHY do I need another function wrapper? If you would use just the handler and pass the parameters, … Read more