Nukiloco

I have a tsconfig.json, and its not actually a default input tag, its a custom component that's called ``Input``.

Is this still an issue with the modern versions of Super Productivity?

I have never worked or contributed on a npm repo before so if I did it would be my first time. Also I think this is where the ``$houdini`` folder...

After reading this, I'm still confused on why there would be two config options here instead of one which should just be a path.

Will there be a fix to this? I love the Path Intellisense extension but sadly the Svelte extension doesn't work with it. Edit: To make ``Path Intellisense`` extension work with...

This is not on the website or a web browser. This is using fetch inside the vitejs config itself.

This is the configuration file: ``` module.exports = { parser: '@typescript-eslint/parser', // add the TypeScript parser plugins: [ 'svelte3', '@typescript-eslint', // add the TypeScript plugin '@html-eslint' ], overrides: [ //...

``` class Apple { seeds: number } ``` This is the minimal reproduction that causes the eslint error.

What is the current status of this pull request?

What is the current status of this?