Stibbs
Stibbs
Hi @tomhoad are you able to share the updated code?
Anyone have a clever workaround for this issue?
It would be great if it supported `bind:value` directly. Until then, you can work around it with something like: ```javascript function handleTags(event) { $form.tags = event.detail.tags; } ... ``` I'm...
This may be working as intended? The readme specifies this is for static sitemaps, which I understood as meaning all routes are known, but I think it means the site...
This appears infeasible to implement **properly** because `svelte-sitemap` would need to analyse the prerendered pages for **material changes to the content**. The linked page says: > ... when we say...
> > But how do we to least make the warning disappears? It makes reading (debugging) using server logs, a nightmare. > > @delanyoyoko, there’s no native Supabase way to...
You are not prerendering those routes hence `svelte-sitemap` does not see them. Refer to the [SvelteKit docs](https://kit.svelte.dev/docs/page-options) but as an example: your `routes/login/+page.svelte` will be server side rendered unless you...
> However, I can't figure out how to get the CSS file to be created in a production build. You probably need to add a build step (in GitHub Actions...