Skip to content

Latest commit

 

History

History
78 lines (52 loc) · 2.15 KB

script-setup-uses-vars.md

File metadata and controls

78 lines (52 loc) · 2.15 KB
pageClass sidebarDepth title description since
rule-details
0
vue/script-setup-uses-vars
prevent `<script setup>` variables used in `<template>` to be marked as unused
v7.13.0

vue/script-setup-uses-vars

prevent <script setup> variables used in <template> to be marked as unused

  • ⚠️ This rule was deprecated.

::: tip

This rule is not needed when using vue-eslint-parser v9.0.0 or later.

:::

ESLint no-unused-vars rule does not detect variables in <script setup> used in <template>. This rule will find variables in <script setup> used in <template> and mark them as used.

This rule only has an effect when the no-unused-vars rule is enabled.

📖 Rule Details

Without this rule this code triggers warning:

<script setup>
  // imported components are also directly usable in template
  import Foo from './Foo.vue'
  import { ref } from 'vue'

  // write Composition API code just like in a normal setup()
  // but no need to manually return everything
  const count = ref(0)
  const inc = () => {
    count.value++
  }
</script>

<template>
  <Foo :count="count" @click="inc" />
</template>

After turning on, Foo is being marked as used and no-unused-vars rule doesn't report an issue.

🔇 When Not To Use It

You can disable this rule in any of the following cases:

  • You are using vue-eslint-parser v9.0.0 or later.
  • You are not using <script setup>.
  • You do not use the no-unused-vars rule.

👫 Related Rules

📚 Further Reading

🚀 Version

This rule was introduced in eslint-plugin-vue v7.13.0

🔍 Implementation