TypeScript Support (EN)

A static type system can help prevent many potential runtime errors, especially as applications grow.

That's why Nuxt's brand new @nuxt/typescript package ships built-in TypeScript tooling support:

  • Nuxt official type definitions
  • Autocompletion in IDE
  • Write everything in TypeScript fashion (layouts, pages, components, plugins, store)
  • Runtime TS support (nuxt.config.ts, modules, serverMiddlewares)
  • TSX Support

Get started

To use TypeScript in your project, install @nuxt/typescript in devDependencies and ts-node in dependencies:

npm i -D @nuxt/typescript
npm i ts-node
# OR
yarn add -D @nuxt/typescript
yarn add ts-node

INFO: @nuxt/typescript ships typescript-related dependencies needed to compile TypeScript files & check types in a separate process.

INFO: ts-node extends @nuxt/core to enable runtime TypeScript support for nuxt.config.ts & serverMiddlewares.

You'll also need to create an empty tsconfig.json file in your root project folder, through either a code editor or command line:

touch tsconfig.json

INFO: The tsconfig.json file will automatically update with default values the first time you run the nuxt command.

From JavaScript to TypeScript

Configuration file

To use TypeScript in your configuration file, all you need to do is rename nuxt.config.js in your root project folder to nuxt.config.ts.

Nuxt.js also brings type definitions which provides autocompletion and type checking:

import NuxtConfiguration from '@nuxt/config'

const config: NuxtConfiguration = {
  // Type or Press `Ctrl + Space` for autocompletion

export default config


For components, we highly advise you to use vue-property-decorator which depends on vue-class-component.

Here is a basic example of mixing a page with a reusable component to display data fetched with Nuxt's asyncData method.

/* models/Post.ts */

export default interface Post {
  id: number
  title: string
  description: string
<!-- components/PostPreview.vue -->

    <h2>{{ post.title }}</h2>
    <p>{{ post.description }}</p>

<script lang="ts">
import { Component, Vue, Prop } from 'vue-property-decorator'
import Post from '~/models/Post'

export default class PostPreview extends Vue {
  @Prop({ type: Object, required: true }) post!: Post
<!-- pages/feed.vue -->

    <PostPreview v-for="post in posts" :key="post.id" :post="post" />

<script lang="ts">
import axios from 'axios'
import { Component, Vue } from 'vue-property-decorator'
import Post from '~/models/Post'

  components: {
    PostPreview: () => import('~/components/PostPreview.vue')
  async asyncData () {
    let { data } = await axios.get(`https://my-api/posts`)
    return {
      posts: data

export default class FeedPage extends Vue {
  posts: Post[] = []

You can use the exact same logic for layouts.

Linting with ESLint

If you're using ESLint to lint your project, here is how you can make ESLint lint your TypeScript files.

IMPORTANT: We're assuming you have already set up nuxt/eslint-config within your project.

First, you need to install @typescript-eslint/eslint-plugin and @typescript-eslint/parser (GitHub monorepo for typescript-eslint):

npm i -D @typescript-eslint/eslint-plugin @typescript-eslint/parser
# OR
yarn add -D @typescript-eslint/eslint-plugin @typescript-eslint/parser

Then, edit your ESLint configuration .eslintrc.js by adding the @typescript-eslint plugin and making @typescript-eslint/parser the default parser.

A minimal configuration should look like this:

module.exports = {
  plugins: ['@typescript-eslint'],
  parserOptions: {
    parser: '@typescript-eslint/parser'
  extends: [
  rules: {
    '@typescript-eslint/no-unused-vars': 'error'

Finally, add or edit the lint script of your package.json:

"lint": "eslint --ext .ts,.js,.vue --ignore-path .gitignore ."

INFO: The --ignore-path option is useful in preventing ESLint from linting files/folders like node_modules, .nuxt or any others you don't want to lint.

You can now lint your TypeScript files by running npm run lint (or yarn lint).

Vous avez vu une erreur ou vous souhaitez contribuer à la documentation ? Éditez cette page sur GitHub !