- Distinct code requirements/dependencies
- Clearly defined expected errors
- Logging
I don't really use the Effect schema, because Valibot is my preferred validator.
- Distinct code requirements/dependencies
- Clearly defined expected errors
- Logging
I don't really use the Effect schema, because Valibot is my preferred validator.
github.com/sillvva/ddal...
github.com/sillvva/ddal...
github.com/sillvva/ddal...
github.com/sillvva/ddal...
I setup most of the Effect code in `$lib/server/effect`
github.com/sillvva/ddal...
And added the managed runtime to `locals` so that it can be accessed by my custom `run` functions in `runtime.ts`
github.com/sillvva/ddal...
I setup most of the Effect code in `$lib/server/effect`
github.com/sillvva/ddal...
And added the managed runtime to `locals` so that it can be accessed by my custom `run` functions in `runtime.ts`
github.com/sillvva/ddal...
I might also make a blog post about how I integrated it with SvelteKit.
I might also make a blog post about how I integrated it with SvelteKit.
github.com/sveltejs/esl...
{
rules: {
"svelte/no-navigation-without-resolve": "off"
}
},
github.com/sveltejs/esl...
{
rules: {
"svelte/no-navigation-without-resolve": "off"
}
},
Testing some more, I seem to be able to enable remote functions so long as I don't enable async, so the issue is only there.
Remote functions are awesome!
Testing some more, I seem to be able to enable remote functions so long as I don't enable async, so the issue is only there.
Remote functions are awesome!
...Damn!
...Damn!
Basically properties of `data` become undefined before navigating away from a page, and the effects try to rerun before that happens so it causes a "reading property of undefined error" on the previous page.
There's a repro in the issue.
Basically properties of `data` become undefined before navigating away from a page, and the effects try to rerun before that happens so it causes a "reading property of undefined error" on the previous page.
There's a repro in the issue.