Registry / testing / eslint-plugin-quasar

eslint-plugin-quasar

library1.1.0jsnpmunverified

Official ESLint plugin for enforcing best practices and aiding migration in Quasar Framework projects. Current version is 1.1.0 (stable), with an alpha cycle leading to 1.0.0. It provides rules to detect deprecated Quasar v0.17 components, directives, CSS, plugins, and properties, and validates props for v1+ components. Key differentiators: official plugin from the Quasar team, focused on migration and prop validation, with legacy and standard configurations. Release cadence is irregular; updates are driven by framework changes.

testing

npm install eslint-plugin-quasar

github ↗package ↗homepage ↗

INSTALL

IMPORT

SIG · ESLINT-PLUGIN-QUAS

eslint-plugin-quasar

testingjavascriptv1.1.0

Install

—

Import

—

Disk

—

Pass rate

0/ 6

Env Coverage0 / 6

glibc

18–22

musl

18–22

Install & Compatibility

Where this runs

tested against v? · npm install

Install × environment matrix

Each cell = how many times install + import succeeded across repeated harness runs. Partial = flaky.
glibc = Debian/Ubuntu slim · musl = Alpine Linux

musl

node 18–226 runs

build_error

glibc

node 18–226 runs

build_error

Code

Verified usage

Verified import paths — ran on the pinned version, not inferred.

plugin default

✓ plugins: ['quasar']

✗ plugins: ['eslint-plugin-quasar']

In .eslintrc, use shorthand 'quasar' for the plugin name.

legacy config

✓ extends: ['plugin:quasar/legacy']

✗ extends: ['quasar/legacy']

Must include 'plugin:' prefix when extending a plugin's config.

standard config

✓ extends: ['plugin:quasar/standard']

✗ extends: ['quasar/standard']

For Quasar v1+ projects, use the standard config.

rule 'no-legacy-components'

✓ rules: { 'quasar/no-legacy-components': 'error' }

✗ rules: { 'no-legacy-components': 'error' }

Rules must be prefixed with 'quasar/'

Basic ESLint configuration for Quasar v1+ using the standard config and two rules.

// .eslintrc.js module.exports = { root: true, env: { node: true }, extends: [ 'plugin:quasar/standard' ], plugins: ['quasar'], rules: { 'quasar/no-invalid-props': 'error', 'quasar/no-invalid-qfield-usage': 'warn' } };

Debug

Known issues

deprecatedThe rule 'check-valid-props' has been deprecated since v1.0.0.

fix

Replace 'check-valid-props' with 'no-invalid-props'.

affects: >=1.0.0

gotchaGlobal ESLint installation requires global plugin installation.

fix

Install eslint and plugins locally for consistency: npm install --save-dev eslint eslint-plugin-quasar

affects: >=0.0.0

gotchaLegacy rules are only for migrating from v0.17 to v1; not relevant for new v1+ projects.

fix

Use the standard config and rules for v1+ projects.

affects: >=1.0.0

breakingIn v1.0.0-alpha.13, directive rule required 'v-' prefix; previously it did not.

fix

Ensure directives in rules include 'v-' prefix (e.g., 'v-model' instead of 'model').

affects: >=1.0.0-alpha.13

Errors

Common errors & fixes

ESLint couldn't find the plugin "eslint-plugin-quasar".

Plugin not installed or not in node_modules.

fix

Run npm install --save-dev eslint-plugin-quasar or ensure it's in devDependencies.

Configuration for rule "quasar/no-legacy-components" is invalid: Value "error" is not a valid severity.

Using string 'error' in older ESLint versions (pre-v6).

fix

Use numeric severity: 2 for error, 1 for warn.

Definition for rule 'quasar/no-invalid-props' was not found.

Incorrect plugin name or rule not available in version.

fix

Ensure plugin is in plugins array and rule name is correct; update to latest version.

Cannot find module 'eslint-plugin-quasar'

Plugin not installed or missing from package.json.

fix

npm install --save-dev eslint-plugin-quasar

Upgrade

Version history

1.1.0latest on npm

Audit

Dependencies

eslintrequiredpeer dependency required for plugin to work

Agent activity

2 hits · last 30 days

node

Resources

githubhttps://github.com/quasarframework/eslint-plugin-quasar ↗

packagehttps://www.npmjs.com/package/eslint-plugin-quasar ↗

homepagehttps://quasar.dev ↗