Ben Woodward

The code makes no sense, but it's syntactically correct: ```svelte // deps import { useQuery, useMutation } from '@sveltestack/svelte-query'; import { onMount, onDestroy } from 'svelte'; // stores import {...

What makes sense to me is for the `{` in `{#await promise}` to jump to `}`. The `#await` keyword should jump to the `/` or `a` in `{/await}`. As for...

this seems like a good alternative: https://github.com/kucherenko/jscpd

Works on Big Sur 11.3 for me.

You absolutely can import components when doing SSR. I'm working on app that relies on this. The error you're seeing [can be caused by different things](https://xperimentalhamid.com/how-do-i/fix-cannot-use-import-statement-outside-a-module/) it seems. It could...

Maybe you missed my edit: > EDIT: Oops just realised that ESM exists, changed my import statement to import { waitUntil } from 'async-wait-until/dist/es.js'; but still getting an error

Thanks 👍🏻, I'll test it later today.

Okay, I've done a bunch more testing and created a reproduction issue. I think this is potentially a bug with SvelteKit/Vite. SvelteKit issue: https://github.com/sveltejs/kit/issues/1498 Reproduction repo: https://github.com/benwoodward/sveltekit-named-export-issue-repro

Still having issues with this unfortunately.. I've done some more testing locally based on suggestions from Svelte team. What I've found is that importing as an ES module only works...

This seems like an obvious feature to add, given that so many websites nowadays use onClick handlers on elements rather than anchor tags or buttons. Vimium is just not usable...