Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / sveltejs/eslint-plugin-svelte3 issues and pull requests
#206 - Linting for svetle file with lang="ts" not matching typescript file linting
Issue -
State: open - Opened by AaronNBrock over 1 year ago
#205 - chore: FIx test
Pull Request -
State: closed - Opened by baseballyama over 1 year ago
#204 - [chore] Deprecate this repository
Pull Request -
State: closed - Opened by baseballyama over 1 year ago
- 3 comments
#203 - False positive for `@typescript-eslint/no-unnecessary-condition` with `export let`
Issue -
State: open - Opened by kevincox over 1 year ago
#202 - False positives for `no-unused-vars` for enum variants
Issue -
State: closed - Opened by kevincox over 1 year ago
- 1 comment
#201 - Slot props produce `no-undef` error on <slot>
Issue -
State: open - Opened by janosh over 1 year ago
#201 - Slot props produce `no-undef` error on <slot>
Issue -
State: open - Opened by janosh over 1 year ago
#200 - Incompatible plugin: eslint-plugin-tailwindcss
Issue -
State: open - Opened by jrouleau almost 2 years ago
#200 - Incompatible plugin: eslint-plugin-tailwindcss
Issue -
State: open - Opened by jrouleau almost 2 years ago
#199 - Force using TypeScript (force lang='ts')
Issue -
State: open - Opened by bosung90 almost 2 years ago
#199 - Force using TypeScript (force lang='ts')
Issue -
State: open - Opened by bosung90 almost 2 years ago
- 1 comment
#198 - [doc] fix broken link to ESLint "Typed Linting"
Pull Request -
State: closed - Opened by meyermarcel almost 2 years ago
#198 - [doc] fix broken link to ESLint "Typed Linting"
Pull Request -
State: closed - Opened by meyermarcel almost 2 years ago
#197 - `@typescript-eslint/no-unsafe-argument`/`no-unsafe-return` false positive in svelte code but not in script tag
Issue -
State: open - Opened by DetachHead almost 2 years ago
- 1 comment
#196 - no-multiple-emty-lines when iterating a store with each block
Issue -
State: open - Opened by mckravchyk about 2 years ago
#195 - Add globals.svelte to README.md example config
Pull Request -
State: closed - Opened by ZerdoX-x about 2 years ago
#195 - Add globals.svelte to README.md example config
Pull Request -
State: closed - Opened by ZerdoX-x about 2 years ago
#194 - ESlint false positive with custom component.
Issue -
State: open - Opened by ptrxyz about 2 years ago
#193 - No documentation how to override rules
Issue -
State: open - Opened by ToP29 about 2 years ago
- 3 comments
#193 - No documentation how to override rules
Issue -
State: open - Opened by ToP29 about 2 years ago
- 3 comments
#192 - Issue with global $$Props interface
Issue -
State: closed - Opened by ZerdoX-x about 2 years ago
- 2 comments
#191 - `@typescript-eslint/no-unnecessary-condition` false positive when property is defined anywhere other than the last line of `script` tag
Issue -
State: open - Opened by DetachHead about 2 years ago
- 1 comment
#191 - `@typescript-eslint/no-unnecessary-condition` false positive when property is defined anywhere other than the last line of `script` tag
Issue -
State: open - Opened by DetachHead about 2 years ago
- 1 comment
#190 - `eslint-disable-next-line` comments don't work in html
Issue -
State: open - Opened by DetachHead about 2 years ago
#189 - incorrect `any` errors when using `await`/`then` block
Issue -
State: open - Opened by DetachHead about 2 years ago
- 1 comment
#189 - incorrect `any` errors when using `await`/`then` block
Issue -
State: open - Opened by DetachHead about 2 years ago
- 3 comments
#188 - `indent` rule not working on `.svelte` files?
Issue -
State: open - Opened by aradalvand about 2 years ago
#187 - svelte-subcomponent-preprocessor
Issue -
State: open - Opened by lichstam about 2 years ago
#186 - Error when destructing local const
Issue -
State: closed - Opened by DanielRios549 over 2 years ago
- 1 comment
#185 - Unexpected character '@' when using {@const}
Issue -
State: closed - Opened by ptelad over 2 years ago
- 2 comments
#184 - This plugin is deprecated in favor of `eslint-plugin-svelte`
Issue -
State: open - Opened by JounQin over 2 years ago
- 6 comments
#183 - How to support both js and ts components?
Issue -
State: closed - Opened by shir0u over 2 years ago
- 1 comment
#182 - variable was used before it was defined (eslint: no-use-before-define)
Issue -
State: open - Opened by axelthat over 2 years ago
- 2 comments
#182 - variable was used before it was defined (eslint: no-use-before-define)
Issue -
State: open - Opened by axelthat over 2 years ago
- 2 comments
#181 - No lock file of package manager are committed
Issue -
State: closed - Opened by mcmxcdev over 2 years ago
- 1 comment
#180 - eslint --fix messing up file, adding duplicated content
Issue -
State: open - Opened by CherryDT over 2 years ago
- 2 comments
#179 - Eslint parse token error with class properties
Issue -
State: open - Opened by Nukiloco over 2 years ago
- 3 comments
#179 - Eslint parse token error with class properties
Issue -
State: open - Opened by Nukiloco over 2 years ago
- 3 comments
#178 - Drop Node 10 and 12. Upgrade to eslint 8
Pull Request -
State: closed - Opened by benmccann over 2 years ago
- 6 comments
#177 - [typescript] Some issues with generic types
Issue -
State: open - Opened by orblazer over 2 years ago
#176 - [typescript] Error `no-unsafe-call` on store in module
Issue -
State: open - Opened by orblazer over 2 years ago
#175 - [typescript] Error `no-use-before-define` when no use before
Issue -
State: open - Opened by orblazer over 2 years ago
- 1 comment
#174 - @const variables used in style directives give "no-unused-vars"
Issue -
State: open - Opened by johnnysprinkles over 2 years ago
- 4 comments
#173 - [fix] ignore css-unused-selector rule if <style global>
Pull Request -
State: open - Opened by metonym over 2 years ago
- 2 comments
#172 - @const raises a "no-undef" false positive
Issue -
State: closed - Opened by kevin-legion almost 3 years ago
- 3 comments
#171 - eslint doesn't work
Issue -
State: closed - Opened by Alexandre-Fernandez almost 3 years ago
- 3 comments
#170 - Incompatibilty with html-eslint
Issue -
State: open - Opened by Nukiloco almost 3 years ago
- 2 comments
#169 - fix(#168): fixes parse errors caused by parentheses
Pull Request -
State: closed - Opened by GauBen almost 3 years ago
- 2 comments
#169 - fix(#168): fixes parse errors caused by parentheses
Pull Request -
State: open - Opened by GauBen almost 3 years ago
- 1 comment
#168 - `Parsing error: Identifier expected.` with SvelteKit
Issue -
State: open - Opened by GauBen almost 3 years ago
#168 - `Parsing error: Identifier expected.` with SvelteKit
Issue -
State: open - Opened by GauBen almost 3 years ago
#168 - `Parsing error: Identifier expected.` with SvelteKit
Issue -
State: open - Opened by GauBen almost 3 years ago
#168 - `Parsing error: Identifier expected.` with SvelteKit
Issue -
State: open - Opened by GauBen almost 3 years ago
#167 - Parsing errors when destructuring store with TypeScript.
Issue -
State: open - Opened by NickAlvesX almost 3 years ago
#167 - Parsing errors when destructuring store with TypeScript.
Issue -
State: open - Opened by NickAlvesX almost 3 years ago
#167 - Parsing errors when destructuring store with TypeScript.
Issue -
State: open - Opened by NickAlvesX almost 3 years ago
#167 - Parsing errors when destructuring store with TypeScript.
Issue -
State: open - Opened by NickAlvesX almost 3 years ago
#166 - [fix] object destructuring bug using `@const`
Pull Request -
State: closed - Opened by si3nloong almost 3 years ago
- 1 comment
#165 - [fix] added import/prefer-default-export (#119)
Pull Request -
State: closed - Opened by jis3r almost 3 years ago
- 3 comments
#165 - [fix] added import/prefer-default-export (#119)
Pull Request -
State: closed - Opened by jis3r almost 3 years ago
- 3 comments
#164 - Object destructuring in @const
Issue -
State: closed - Opened by janosh almost 3 years ago
#163 - Unsafe member access in templates
Issue -
State: open - Opened by enyo almost 3 years ago
- 3 comments
#162 - Combination of `'svelte3/named-blocks': true` and TypeScript parser does not work
Issue -
State: open - Opened by compeek almost 3 years ago
#162 - Combination of `'svelte3/named-blocks': true` and TypeScript parser does not work
Issue -
State: open - Opened by compeek almost 3 years ago
#162 - Combination of `'svelte3/named-blocks': true` and TypeScript parser does not work
Issue -
State: open - Opened by compeek almost 3 years ago
#162 - Combination of `'svelte3/named-blocks': true` and TypeScript parser does not work
Issue -
State: open - Opened by compeek almost 3 years ago
#161 - [feat] support for `{@const}`
Pull Request -
State: closed - Opened by ota-meshi almost 3 years ago
#161 - [feat] support for `{@const}`
Pull Request -
State: closed - Opened by ota-meshi almost 3 years ago
#161 - [feat] support for `{@const}`
Pull Request -
State: closed - Opened by ota-meshi almost 3 years ago
#161 - [feat] support for `{@const}`
Pull Request -
State: closed - Opened by ota-meshi almost 3 years ago
#160 - (fix) better fix range handling
Pull Request -
State: closed - Opened by dummdidumm almost 3 years ago
#160 - (fix) better fix range handling
Pull Request -
State: closed - Opened by dummdidumm almost 3 years ago
#159 - [fix] add injected globals to ts when there's no instance script
Pull Request -
State: closed - Opened by dummdidumm almost 3 years ago
#159 - [fix] add injected globals to ts when there's no instance script
Pull Request -
State: closed - Opened by dummdidumm almost 3 years ago
#158 - [fix] allow $$Props, $$Slots, $$Events usage
Pull Request -
State: closed - Opened by dummdidumm almost 3 years ago
#158 - [fix] allow $$Props, $$Slots, $$Events usage
Pull Request -
State: closed - Opened by dummdidumm almost 3 years ago
#157 - Using no-lonely-if makes code broken
Issue -
State: closed - Opened by warmrobot almost 3 years ago
- 1 comment
#157 - Using no-lonely-if makes code broken
Issue -
State: closed - Opened by warmrobot almost 3 years ago
- 1 comment
#156 - Using no-else-return makes code broken
Issue -
State: closed - Opened by warmrobot almost 3 years ago
- 1 comment
#156 - Using no-else-return makes code broken
Issue -
State: closed - Opened by warmrobot almost 3 years ago
- 1 comment
#156 - Using no-else-return makes code broken
Issue -
State: closed - Opened by warmrobot almost 3 years ago
- 1 comment
#155 - Use TS 4.5 `preserveValueImports` if it's available
Pull Request -
State: closed - Opened by Monkatraz almost 3 years ago
- 4 comments
#155 - Use TS 4.5 `preserveValueImports` if it's available
Pull Request -
State: closed - Opened by Monkatraz almost 3 years ago
- 4 comments
#154 - Support using TypeScript 4.5 `preserveValueImports`
Issue -
State: closed - Opened by Monkatraz almost 3 years ago
#154 - Support using TypeScript 4.5 `preserveValueImports`
Issue -
State: closed - Opened by Monkatraz almost 3 years ago
#154 - Support using TypeScript 4.5 `preserveValueImports`
Issue -
State: closed - Opened by Monkatraz almost 3 years ago
#154 - Support using TypeScript 4.5 `preserveValueImports`
Issue -
State: closed - Opened by Monkatraz almost 3 years ago
#153 - CSS custom properties handled as errors
Issue -
State: closed - Opened by nosovk almost 3 years ago
- 2 comments
#153 - CSS custom properties handled as errors
Issue -
State: closed - Opened by nosovk almost 3 years ago
- 2 comments
#153 - CSS custom properties handled as errors
Issue -
State: closed - Opened by nosovk almost 3 years ago
- 2 comments
#152 - Javascript Keywords as Props - Error
Issue -
State: closed - Opened by jvanderen1 almost 3 years ago
- 1 comment
#152 - Javascript Keywords as Props - Error
Issue -
State: closed - Opened by jvanderen1 almost 3 years ago
- 1 comment
#152 - Javascript Keywords as Props - Error
Issue -
State: closed - Opened by jvanderen1 almost 3 years ago
- 1 comment
#152 - Javascript Keywords as Props - Error
Issue -
State: closed - Opened by jvanderen1 almost 3 years ago
- 1 comment
#151 - Question: is there support to check whether <button> has a type?
Issue -
State: open - Opened by josdejong almost 3 years ago
#151 - Question: is there support to check whether <button> has a type?
Issue -
State: open - Opened by josdejong almost 3 years ago
#151 - Question: is there support to check whether <button> has a type?
Issue -
State: open - Opened by josdejong almost 3 years ago
#150 - Rebase v3.2.1
Pull Request -
State: closed - Opened by arjunkalburgi almost 3 years ago
- 1 comment
#150 - Rebase v3.2.1
Pull Request -
State: closed - Opened by arjunkalburgi almost 3 years ago
- 1 comment
#150 - Rebase v3.2.1
Pull Request -
State: closed - Opened by arjunkalburgi almost 3 years ago
- 1 comment