Introduction

eslint-plugin-svelte is the official ESLint plugin for Svelte.
It leverages the AST generated by svelte-eslint-parser to provide custom linting for Svelte.
Note that eslint-plugin-svelte and svelte-eslint-parser cannot be used alongside eslint-plugin-svelte3.

Installation

1npm install --save-dev svelte eslint eslint-plugin-svelte globals

[!NOTE]

Requirements:

• ESLint v8.57.1, v9.0.0, and above
• Node.js v18.18.0, v20.9.0, v21.1.0 and above

Usage

Use the eslint.config.js file to configure rules. For more details, see the ESLint documentation.

Configuration

JavaScript project

1// eslint.config.js
2import js from '@eslint/js';
3import svelte from 'eslint-plugin-svelte';
4import globals from 'globals';
5import svelteConfig from './svelte.config.js';
6
7/** @type {import('eslint').Linter.Config[]} */
8export default [
9  js.configs.recommended,
10  ...svelte.configs.recommended,
11  {
12    languageOptions: {
13      globals: {
14        ...globals.browser,
15        ...globals.node // Add this if you are using SvelteKit in non-SPA mode
16      }
17    }
18  },
19  {
20    files: ['**/*.svelte', '**/*.svelte.js'],
21    languageOptions: {
22      parserOptions: {
23        // We recommend importing and specifying svelte.config.js.
24        // By doing so, some rules in eslint-plugin-svelte will automatically read the configuration and adjust their behavior accordingly.
25        // While certain Svelte settings may be statically loaded from svelte.config.js even if you don’t specify it,
26        // explicitly specifying it ensures better compatibility and functionality.
27        svelteConfig
28      }
29    }
30  },
31  {
32    rules: {
33      // Override or add rule settings here, such as:
34      // 'svelte/rule-name': 'error'
35    }
36  }
37];

TypeScript project

1npm install --save-dev typescript-eslint

1// eslint.config.js
2import js from '@eslint/js';
3import svelte from 'eslint-plugin-svelte';
4import globals from 'globals';
5import ts from 'typescript-eslint';
6import svelteConfig from './svelte.config.js';
7
8export default ts.config(
9  js.configs.recommended,
10  ...ts.configs.recommended,
11  ...svelte.configs.recommended,
12  {
13    languageOptions: {
14      globals: {
15        ...globals.browser,
16        ...globals.node
17      }
18    }
19  },
20  {
21    files: ['**/*.svelte', '**/*.svelte.ts', '**/*.svelte.js'],
22    // See more details at: https://typescript-eslint.io/packages/parser/
23    languageOptions: {
24      parserOptions: {
25        projectService: true,
26        extraFileExtensions: ['.svelte'], // Add support for additional file extensions, such as .svelte
27        parser: ts.parser,
28        // Specify a parser for each language, if needed:
29        // parser: {
30        //   ts: ts.parser,
31        //   js: espree,    // Use espree for .js files (add: import espree from 'espree')
32        //   typescript: ts.parser
33        // },
34
35        // We recommend importing and specifying svelte.config.js.
36        // By doing so, some rules in eslint-plugin-svelte will automatically read the configuration and adjust their behavior accordingly.
37        // While certain Svelte settings may be statically loaded from svelte.config.js even if you don’t specify it,
38        // explicitly specifying it ensures better compatibility and functionality.
39        svelteConfig
40      }
41    }
42  },
43  {
44    rules: {
45      // Override or add rule settings here, such as:
46      // 'svelte/rule-name': 'error'
47    }
48  }
49);

[!WARNING] The TypeScript parser uses a singleton internally, meaning it only respects the options provided during its initial initialization. If you try to change the options for a different file or override them later, the parser will ignore the new options, which may lead to errors. For more context, see typescript-eslint/typescript-eslint#6778.

Available Configurations

This plugin provides the following configurations:

• eslintPluginSvelte.configs.base ... Enables correct Svelte parsing.
• eslintPluginSvelte.configs.recommended ... Includes base configuration, plus rules to prevent errors or unintended behavior.
• eslintPluginSvelte.configs.prettier ... Disables rules that may conflict with Prettier. You still need to configure Prettier to work with Svelte manually, for example, by using prettier-plugin-svelte.
• eslintPluginSvelte.configs.all ... Includes all available rules. Note: This configuration is not recommended for production use, as it changes with every minor and major version of eslint-plugin-svelte. Use at your own risk.

For more details, see the rule list to explore the rules provided by this plugin.

settings.svelte

You can customize the behavior of this plugin using specific settings.

1// eslint.config.js
2export default [
3  // ...
4  {
5    settings: {
6      svelte: {
7        // Specifies an array of rules to ignore reports within the template.
8        // For example, use this to disable rules in the template that may produce unavoidable false positives.
9        ignoreWarnings: [
10          '@typescript-eslint/no-unsafe-assignment',
11          '@typescript-eslint/no-unsafe-member-access'
12        ],
13        // Specifies options for Svelte compilation.
14        // This affects rules that rely on Svelte compilation,
15        // such as svelte/valid-compile and svelte/no-unused-svelte-ignore.
16        // Note that this setting does not impact ESLint’s custom parser.
17        compileOptions: {
18          // Specifies options related to PostCSS. You can disable the PostCSS processing by setting it to false.
19          postcss: {
20            // Specifies the path to the directory that contains the PostCSS configuration.
21            configFilePath: './path/to/my/postcss.config.js'
22          }
23        },
24        // Even if settings.svelte.kit is not specified, the rules will attempt to load information from svelte.config.js.
25        // However, if the default behavior does not work as expected, you should specify settings.svelte.kit explicitly.
26        // If you are using SvelteKit with a non-default configuration, you need to set the following options.
27        // The schema is a subset of SvelteKit’s configuration, so refer to the SvelteKit documentation for more details.
28        // https://svelte.dev/docs/kit/configuration
29        kit: {
30          files: {
31            routes: 'src/routes'
32          }
33        }
34      }
35    }
36  }
37  // ...
38];

Editor Integrations

Visual Studio Code
Install dbaeumer.vscode-eslint.
Configure .svelte files in .vscode/settings.json:

1{
2  "eslint.validate": ["javascript", "javascriptreact", "svelte"]
3}

Migration Guide

If you’re migrating from eslint-plugin-svelte v1 or @ota-meshi/eslint-plugin-svelte, see the migration guide.

Versioning Policy

This project follows Semantic Versioning. Unlike ESLint’s versioning policy, new rules may be added to the recommended config in minor releases. If these rules cause unwanted warnings, you can disable them.

Rules

:wrench: Indicates that the rule is fixable, and using --fix option on the command line can automatically fix some of the reported problems.
:bulb: Indicates that some problems reported by the rule are manually fixable by editor suggestions.
:star: Indicates that the rule is included in the plugin:svelte/recommended config.

Possible Errors

These rules relate to possible syntax or logic errors in Svelte code:

Rule ID	Description
svelte/infinite-reactive-loop	Svelte runtime prevents calling the same reactive statement twice in a microtask. But between different microtask, it doesn't prevent.	:star:
svelte/no-dom-manipulating	disallow DOM manipulating	:star:
svelte/no-dupe-else-if-blocks	disallow duplicate conditions in {#if} / {:else if} chains	:star:
svelte/no-dupe-on-directives	disallow duplicate on: directives	:star:
svelte/no-dupe-style-properties	disallow duplicate style properties	:star:
svelte/no-dupe-use-directives	disallow duplicate use: directives	:star:
svelte/no-not-function-handler	disallow use of not function in event handler	:star:
svelte/no-object-in-text-mustaches	disallow objects in text mustache interpolation	:star:
svelte/no-raw-special-elements	Checks for invalid raw HTML elements	:star::wrench:
svelte/no-reactive-reassign	disallow reassigning reactive values	:star:
svelte/no-shorthand-style-property-overrides	disallow shorthand style properties that override related longhand properties	:star:
svelte/no-store-async	disallow using async/await inside svelte stores because it causes issues with the auto-unsubscribing features	:star:
svelte/no-top-level-browser-globals	disallow using top-level browser global variables
svelte/no-unknown-style-directive-property	disallow unknown style:property	:star:
svelte/require-store-callbacks-use-set-param	store callbacks must use set param	:bulb:
svelte/require-store-reactive-access	disallow to use of the store itself as an operand. Need to use $ prefix or get function.	:star::wrench:
svelte/valid-compile	disallow warnings when compiling.
svelte/valid-style-parse	require valid style element parsing

Security Vulnerability

These rules relate to security vulnerabilities in Svelte code:

Rule ID	Description
svelte/no-at-html-tags	disallow use of {@html} to prevent XSS attack	:star:
svelte/no-target-blank	disallow target="_blank" attribute without rel="noopener noreferrer"

Best Practices

These rules relate to better ways of doing things to help you avoid problems:

Rule ID	Description
svelte/block-lang	disallows the use of languages other than those specified in the configuration for the lang attribute of <script> and <style> blocks.	:bulb:
svelte/button-has-type	disallow usage of button without an explicit type attribute
svelte/no-add-event-listener	Warns against the use of addEventListener	:bulb:
svelte/no-at-debug-tags	disallow the use of {@debug}	:star::bulb:
svelte/no-ignored-unsubscribe	disallow ignoring the unsubscribe method returned by the subscribe() on Svelte stores.
svelte/no-immutable-reactive-statements	disallow reactive statements that don't reference reactive values.	:star:
svelte/no-inline-styles	disallow attributes and directives that produce inline styles
svelte/no-inspect	Warns against the use of $inspect directive	:star:
svelte/no-reactive-functions	it's not necessary to define functions in reactive statements	:star::bulb:
svelte/no-reactive-literals	don't assign literal values in reactive statements	:star::bulb:
svelte/no-svelte-internal	svelte/internal will be removed in Svelte 6.	:star:
svelte/no-unnecessary-state-wrap	Disallow unnecessary $state wrapping of reactive classes	:star::bulb:
svelte/no-unused-class-name	disallow the use of a class in the template without a corresponding style
svelte/no-unused-props	Warns about defined Props properties that are unused	:star:
svelte/no-unused-svelte-ignore	disallow unused svelte-ignore comments	:star:
svelte/no-useless-children-snippet	disallow explicit children snippet where it's not needed	:star:
svelte/no-useless-mustaches	disallow unnecessary mustache interpolations	:star::wrench:
svelte/prefer-const	Require const declarations for variables that are never reassigned after declared	:wrench:
svelte/prefer-destructured-store-props	destructure values from object stores for better change tracking & fewer redraws	:bulb:
svelte/prefer-writable-derived	Prefer using writable $derived instead of $state and $effect	:star::bulb:
svelte/require-each-key	require keyed {#each} block	:star:
svelte/require-event-dispatcher-types	require type parameters for createEventDispatcher	:star:
svelte/require-optimized-style-attribute	require style attributes that can be optimized
svelte/require-stores-init	require initial value in store
svelte/valid-each-key	enforce keys to use variables defined in the {#each} block	:star:

Stylistic Issues

These rules relate to style guidelines, and are therefore quite subjective:

Rule ID	Description
svelte/consistent-selector-style	enforce a consistent style for CSS selectors
svelte/derived-has-same-inputs-outputs	derived store should use same variable names between values and callback	:bulb:
svelte/first-attribute-linebreak	enforce the location of first attribute	:wrench:
svelte/html-closing-bracket-new-line	Require or disallow a line break before tag's closing brackets	:wrench:
svelte/html-closing-bracket-spacing	require or disallow a space before tag's closing brackets	:wrench:
svelte/html-quotes	enforce quotes style of HTML attributes	:wrench:
svelte/html-self-closing	enforce self-closing style	:wrench:
svelte/indent	enforce consistent indentation	:wrench:
svelte/max-attributes-per-line	enforce the maximum number of attributes per line	:wrench:
svelte/mustache-spacing	enforce unified spacing in mustache	:wrench:
svelte/no-extra-reactive-curlies	disallow wrapping single reactive statements in curly braces	:bulb:
svelte/no-restricted-html-elements	disallow specific HTML elements
svelte/no-spaces-around-equal-signs-in-attribute	disallow spaces around equal signs in attribute	:wrench:
svelte/prefer-class-directive	require class directives instead of ternary expressions	:wrench:
svelte/prefer-style-directive	require style directives instead of style attribute	:wrench:
svelte/require-event-prefix	require component event names to start with "on"
svelte/shorthand-attribute	enforce use of shorthand syntax in attribute	:wrench:
svelte/shorthand-directive	enforce use of shorthand syntax in directives	:wrench:
svelte/sort-attributes	enforce order of attributes	:wrench:
svelte/spaced-html-comment	enforce consistent spacing after the <!-- and before the --> in a HTML comment	:wrench:

Extension Rules

These rules extend the rules provided by ESLint itself, or other plugins to work well in Svelte:

Rule ID	Description
svelte/no-inner-declarations	disallow variable or function declarations in nested blocks	:star:
svelte/no-trailing-spaces	disallow trailing whitespace at the end of lines	:wrench:

SvelteKit

These rules relate to SvelteKit and its best Practices.

Rule ID	Description
svelte/no-export-load-in-svelte-module-in-kit-pages	disallow exporting load functions in *.svelte module in SvelteKit page components.	:star:
svelte/no-navigation-without-base	disallow using navigation (links, goto, pushState, replaceState) without the base path
svelte/valid-prop-names-in-kit-pages	disallow props other than data or errors in SvelteKit page components.	:star:

Experimental

:warning: These rules are considered experimental and may change or be removed in the future:

Rule ID	Description
svelte/experimental-require-slot-types	require slot type declaration using the $$Slots interface
svelte/experimental-require-strict-events	require the strictEvents attribute on <script> tags

System

These rules relate to this plugin works:

Rule ID	Description
svelte/comment-directive	support comment-directives in HTML template	:star:
svelte/system	system rule for working this plugin	:star:

Deprecated

• :warning: We're going to remove deprecated rules in the next major release. Please migrate to successor/new rules.
• :innocent: We don't fix bugs which are in deprecated rules since we don't have enough resources.

Rule ID	Replaced by
svelte/@typescript-eslint/no-unnecessary-condition	This rule is no longer needed when using svelte-eslint-parser>=v0.19.0.
svelte/no-dynamic-slot-name	Now Svelte compiler itself throws an compile error.
svelte/no-goto-without-base	svelte/no-navigation-without-base

Contributing

Contributions are welcome! Please open an issue or submit a PR. For more details, see CONTRIBUTING.md.
Refer to svelte-eslint-parser for AST details.

License

See LICENSE (MIT).