Mathias Picker

Thank you for answering! I still mean that there are valid use cases where it makes sense to have nested dropdowns, even if it requires an additional click to open....

No worries, thank you for the answer! I agree that it is a gap in the platform, but isn't that what popper.js is trying to solve with the `strategy: fixed`...

I understand that the following barrel file is difficult to transform: ```ts export * from './path-1'; export * from './path-2'; ``` But why are barrel files with named exports slow?...

Is this something that will be addressed in Svelte 5?

This would not work in a normal js/ts file: ```ts const numerator = writable(1); const denominator = writable(1); const fraction = reactive((set) => { set($numerator / $denominator); }); ```

> Hey, I had it working with the following config: > > ```js > import js from "@eslint/js"; > import tsParser from "@typescript-eslint/parser"; > import eslintConfigPrettier from "eslint-config-prettier"; > import...

> Also working for me. According to the rollout tracker there is support. > > * [📈 Tracking: Flat Config rollout eslint/eslint#18093](https://github.com/eslint/eslint/issues/18093) > * [feat: export meta object #467](https://github.com/sveltejs/eslint-plugin-svelte/pull/467) >...

> @MathiasWP : I had the same problem as you, but I got it working by adding `files: ["**/*.svelte"],` to the configuration object block that contains `languageOptions`. > > My...

> For completeness, here is a full `eslint` "flat file" configuration that works for Svelte projects that use TypeScript. It also includes Prettier linting. > > Maybe an example of...

> This should be added to the readme in the parser configuration section. We also don't have to import the ts parser see here [typescript-eslint.io/packages/typescript-eslint/#manually-configuring-our-plugin-and-parser](https://typescript-eslint.io/packages/typescript-eslint/#manually-configuring-our-plugin-and-parser). Thanks, feels nice to remove...