Stepan

@itsgoingd There are at least one use case when you have SPA with SSR and requests to API often happen in backend so you can't actually see responses in browser...

Run into the same problems, and debugged it till this: 1. type=module in package.json 2. all imports should have .js at the end 3. future-detection.js shouldn't just have top-level assumptions...

Thanks for a very quick fix! For anyone searching, this works now in SvelteKit: ``` let inputElement; import { browser } from '$app/environment'; import { onMount } from 'svelte'; onMount(async...

Is there any reason why it has stopPropogation in the first place? Anyway, this workaround is greatly appreciated and would solve #162

Wow, glad I found this issue. I was going crazy about why translations kept doing crazy things on production but always worked locally and on staging. The solution by [lbguilherme](https://github.com/lbguilherme)...

Or at the very least, default classes should come first, that will also partially solve the problem.

@janosh How about changing it to something like: ``` export let outerDivClass = "multiselect" class={outerDivClass} ``` that way if you set it, it will not apply the default class.

So one global switch headlessMode that disables all default classes are fine by you? I can make PR for that.