Setting up TypeScript in Vue project - Why You Should Know This

The Big Idea

Discover how adding TypeScript to Vue saves you hours of debugging and frustration!

The Scenario

Imagine building a Vue app without TypeScript and trying to keep track of all your data types and component props manually.

You constantly worry about passing wrong data or making typos that break your app at runtime.

The Problem

Without TypeScript, errors only show up when you run the app, making debugging slow and frustrating.

You spend extra time hunting down bugs caused by wrong data types or missing properties.

The Solution

Setting up TypeScript in your Vue project helps catch errors early while you write code.

It gives you clear hints and checks for your data, making your app more reliable and easier to maintain.

Before vs After

✗ Before

props: ['title', 'count']
// No type checks, easy to pass wrong data

✓ After

const props = defineProps<{ title: string; count: number }>()
// TypeScript checks props types automatically

What It Enables

You can build Vue apps with confidence, knowing your data types are correct and bugs are caught early.

Real Life Example

Imagine creating a shopping cart component that expects a list of products. TypeScript ensures you always pass the right product data shape, preventing crashes when users add items.

Key Takeaways

Manual type checking in Vue is error-prone and slow.

TypeScript integration catches errors while coding.

It improves app reliability and developer confidence.

Practice

1. What is the main benefit of using TypeScript in a Vue project?

easy

A. It helps catch errors early and improves code clarity.

B. It automatically styles your components.

C. It replaces Vue's template syntax with HTML.

D. It removes the need for JavaScript entirely.

Solution

1. Step 1: Understand TypeScript's role

   TypeScript adds static typing to JavaScript, helping catch errors before running code.

2. Step 2: Relate to Vue projects

   Using TypeScript in Vue improves code clarity and reduces runtime bugs.

3. Final Answer:

   It helps catch errors early and improves code clarity. -> Option A

4. Quick Check:

   TypeScript improves code safety = A [OK]

Hint: TypeScript catches errors before running code [OK]

Common Mistakes:

• Thinking TypeScript styles components
• Confusing TypeScript with HTML templates
• Believing TypeScript removes JavaScript

2. Which command is used to create a new Vue project with TypeScript support?

easy

A. vue create project --typescript

B. npm create vue@latest and select TypeScript option

C. npm install vue typescript

D. vue add typescript

Solution

1. Step 1: Identify the official Vue CLI command

   The recommended way is using npm create vue@latest to start a new project.

2. Step 2: Select TypeScript during setup

   During the interactive setup, you choose TypeScript to enable it.

3. Final Answer:

   npm create vue@latest and select TypeScript option -> Option B

4. Quick Check:

   Use npm create vue@latest for new Vue projects [OK]

Hint: Use npm create vue@latest and pick TypeScript [OK]

Common Mistakes:

• Using old vue CLI commands
• Trying to install TypeScript separately after project creation
• Confusing add commands with create commands

3. Given this Vue component script tag, what is missing to enable TypeScript?

<script>
export default {
  data() {
    return { count: 0 }
  }
}
</script>

medium

A. Wrap the export in a defineComponent call

B. Change data() to setup()

C. Add type="module" to the <script> tag

D. Add lang="ts" attribute to the <script> tag

Solution

1. Step 1: Identify how to enable TypeScript in Vue scripts

   Vue requires lang="ts" on the <script> tag to treat it as TypeScript.

2. Step 2: Check other options

   Changing to setup() or adding type="module" does not enable TypeScript automatically.

3. Final Answer:

   Add lang="ts" attribute to the <script> tag -> Option D

4. Quick Check:

   Use lang="ts" to enable TypeScript [OK]

Hint: Add lang="ts" to script tag for TypeScript [OK]

Common Mistakes:

• Forgetting lang="ts" on script tag
• Confusing setup() with TypeScript enabling
• Assuming type="module" enables TypeScript

4. You added lang="ts" to your Vue component but get errors about missing types. What is the likely cause?

medium

A. You forgot to create or configure tsconfig.json in the project root.

B. You need to remove lang="ts" to fix errors.

C. Vue does not support TypeScript in single file components.

D. You must rename the file extension to .ts instead of .vue.

Solution

1. Step 1: Understand TypeScript configuration needs

   TypeScript requires a tsconfig.json file to know how to compile and check types.

2. Step 2: Check other options

   Removing lang="ts" disables TypeScript, Vue supports TypeScript in .vue files, and renaming files is not needed.

3. Final Answer:

   You forgot to create or configure tsconfig.json in the project root. -> Option A

4. Quick Check:

   tsconfig.json is required for TypeScript setup [OK]

Hint: Create tsconfig.json to avoid missing type errors [OK]

Common Mistakes:

• Removing lang="ts" instead of fixing config
• Thinking Vue disallows TypeScript in .vue files
• Renaming .vue files to .ts incorrectly

5. You want to use TypeScript in a Vue 3 project with the Composition API. Which setup is correct for the script block?

hard

A. <script lang="js" setup>
import { ref } from 'vue'
const count = ref(0)
</script>

B. <script>
import { ref } from 'vue'
const count = ref(0)
</script>

C. <script lang="ts" setup>
import { ref } from 'vue'
const count = ref(0)
</script>

D. <script lang="ts">
export default {
data() { return { count: 0 } }
}
</script>

Solution

1. Step 1: Identify TypeScript and Composition API usage

   Using lang="ts" setup enables TypeScript and Composition API syntax in Vue 3.

2. Step 2: Check other options

   The version with lang="js" setup uses JavaScript not TypeScript, the plain <script> lacks the lang="ts" attribute, and the one using export default with data() is Options API, not Composition API.

3. Final Answer:

   <script lang="ts" setup> with ref import and usage -> Option C

4. Quick Check:

   Use lang="ts" setup for Composition API with TypeScript [OK]

Hint: Use

Common Mistakes:

• Omitting lang="ts" for TypeScript
• Using lang="js" instead of lang="ts"
• Mixing Options API with Composition API syntax