Alternative to copying flyonui.js in Svelte manually to static directory?

[arnoldknott]

It appears a bit error-prone to me, to copy the flyonui.jsmanully into the static directory according to Svelte setup guide step 3 & 4.

this would need to be done again in all future updates and very likely to get missed.

I wonder if adding this

<script>
	const loadHSStaticMethods = async () => {
		const {HSStaticMethods} = await import('flyonui/flyonui.js')
		return HSStaticMethods;
	}

	$effect(()=> {
                afterNavigate( () => {
			loadHSStaticMethods().then((loadedHSStaticMethods) => {
				loadedHSStaticMethods.autoInit();
			})
		})
	})
</script>

to src/routes/+layout.sveltecould do the job automatically and always uses the latest installed version in node_modules?

[arnoldknott]

Here's another way:

<script lang="ts">
	const loadHSStaticMethods = async () => {
		const {HSStaticMethods} = await import('flyonui/flyonui.js')
		return HSStaticMethods;
	}

	const initFlyonui = (_node: HTMLElement) => {
		afterNavigate( () => {
			loadHSStaticMethods().then((loadedHSStaticMethods) => {
				// console.log('layout - client - -effect calling - autoInit')
				loadedHSStaticMethods.autoInit();
			})
		})
	}
</script>
<svelte:window use:initFlyonui />

Unfortunately, I couldn't get `<svelte:window onload={initFlyonui} /> to work. It's not triggering.