Why is setting a store value in load function bad?

Jim Nayzium — Fri, 09 Aug 2024 13:47:52 +0000

Per the sveltekit documentation and the tutorial, it says, "You may be tempted to do this," and then it shows an example of a store value being set inside a load function on your +page.js. It goes on to say that value will be available to all users, and that has confused me.

My particular application needs are solved mosts conveniently by setting a store's value in the +layout.js file, and then dozens of small components reference that store's values instead of always having to every time I use and re-use these components.

I am just confused how setting the store value in the load function on the client side would impact all the users. It reads confusing.

Can someone explain what they mean?
Thanks.

Confused on +layout.js and +layout.svelte props passed in load() function...

Jim Nayzium — Tue, 16 Jul 2024 16:11:29 +0000

I have a load function in my root +layout.js file that is:

export async function load() { // and all it returns is return { prop1: true, prop2: false, prop3: "value 3" };
For the life of me, I cannot do anything in the +layout.svelte file to make these values show up.

export let prop1; export let prop2; export let prop3; console.log("prop1 = " + prop1);

gives me "prop1 undefined" in the console every time!
I have tried deconstructing the export like

let { prop1 } = data; // and let { prop1 } = props;
and nothing works... no matter what I do!

Is it because the load function is async? I need it to be async so I can fetch some external api's when it's done, but I was just testing the bare bones to try and understand how things worked.

Any ideas on the load order of

+page.js vs +layout.js
+page.svelte vs +layout.svelte

etc?

Forem: Jim Nayzium

Why is setting a store value in load function bad?

Confused on +layout.js and +layout.svelte props passed in load() function...