Eric Liu

Surely there's a more "Svelte" way of doing this. Just thinking a loud here. Say that you have a reactive assignment that only tracks non-disabled items: ``` $: enabledResults =...

Here's an adapted [Svelte REPL](https://svelte.dev/repl/8cd2327a580c4f429c71f7df999bd51d?version=3.46.2) that demos a custom threshold (0.5); even changing it to 0.1 should have an effect. I wonder if it could be a styling issue? Is...

You will need to manually type this. ```svelte /** @type {() => void} */ export const x = () => console.log('works') ```

Thanks for raising an issue. Supporting webpack is definitely worth considering.

Thanks for reporting. As a workaround, are you able to omit the `input` property and have the Svelte entry be inferred from the `package.json`? See the [build script used by...

Currently, the markdown/json generation is lagging behind the TypeScript generation, which should not include the actual function code. Labelling this as a bug.

@imperator-maximus What do you expect the value to be for the Markdown/JSON formats? The type instead?

The `@param`, `@returns` is currently not supported. Have you tried defining the entire signature using `@type`? ```js /** @typedef {any} Survival */ /** @type {(cloak: object, dagger: object) => Survival}...

Could you clarify what you mean? The use case for this library is to make plain Svelte components compatible with users who do use `lang="ts"`.

Interesting. So you author components in TS and want them to be consumable by non-TS apps. Just thinking a loud here, but would the following work for you use case?...