Releases

@nuxt/typescript-runtime@2.0.1 1/16/2021

Dependencies

  • Upgrade to TypeScript 4.1
  • Upgrade ts-node : ^9.0.0 -> ^9.1.1

@nuxt/typescript-runtime@0.2.0 10/2/2019

:warning: Important :warning:

Starting @nuxt/typescript-runtime@0.2.0, Nuxt 2.10 or above is required.

Refactor

  • Use Nuxt 2.10 CLI hooks, leading to lighter and much cleaner implementation.

Features

  • Custom tsconfig location with --tsconfig CLI option when using nuxt-ts :

Fixes

  • Fix issues when the .ts extension was not given to serverMiddleware & modules in nuxt.config.ts (#80).
  • Fixes any issues regarding CLI options when using nuxt-ts (i.e. correctly find rootDir).

All of the fixes and the feature provided is only possible thanks to Nuxt 2.10 CLI hooks, that's why 2.10 becomes now the minimal version to have to use last version of Nuxt TS Runtime support package.

@nuxt/typescript-runtime@2.0.0 9/2/2020

Dependencies

  • Upgrade to TypeScript 4
  • Upgrade ts-node : ^8.10.2 -> ^9.0.0

Breaking Changes

  • ts-node@9 dropped support for Node versions < 10

@nuxt/typescript-build@2.0.3 9/2/2020

Dependencies

  • Upgrade to TypeScript 4
  • Upgrade fork-ts-checker-webpack-plugin : ^5.0.14 -> ^5.1.0,
  • Upgrade ts-loader : ^8.0.2 -> ^8.0.3

@nuxt/typescript-build@2.0.0 7/6/2020

Fixes

  • Fixed an issue when using TSX in .vue files (114d69)

Dependencies

Breaking changes

ForkTsCheckerWebpackPlugin v5 has changed its options format and dropped Node 8 support. Follow their documentation if you were customizing options through typescript.typeCheck module option.

Dropped @nuxt/types from @nuxt/typescript-build package, it nows need to be manually installed, documentation has been upgraded.

@nuxt/typescript-build@1.0.0 5/18/2020

Breaking change

Following the end of life of Node 8, ts-loader@7 no longer supports Node 8.

@nuxt/typescript-build has been upgraded to ts-loader@7, so it also no longer supports Node 8.

@nuxt/types@0.7.4 4/11/2020

@nuxt/typescript-build@0.6.1 3/27/2020

  • Update dependency fork-ts-checker-webpack-plugin to v4 (#322) (d8ecab5)

@nuxt/types@0.7.0 3/27/2020

@nuxt/typescript-build@2.0.4 1/16/2021

Dependencies

  • Upgrade to TypeScript 4.1
  • Upgrade fork-ts-checker-webpack-plugin : ^5.2.0 -> ^6.1.0
  • Upgrade ts-loader : ^8.0.4 -> ^8.0.14

TypeScript 4.1

You may have type issues you need to fix while upgrading.

For example a common one is for void Promises you need to explicitly type the return type of the Promise :

new Promise<void>()

instead of

new Promise()

Anyway, your IDE & type checker will tell you what's going wrong and you'll be able to quick fix it !

@nuxt/typescript-build@0.6.0 3/2/2020

  • Upgrade TypeScript to 3.8

@nuxt/typescript-build@0.5.1 12/11/2019

Important

Babel plugins have been removed, it has been found that you need to use es2018 target instead of esnext in your tsconfig.json to have TypeScript 3.7 features.

You may want to add babel plugins back on your own if you think having to use the TypeScript 3.7 features inside Vue templates, but we don't really recommend that as it would make your code hard to be read and shared (for help purpose but also for reusability in non-TS projects).

@nuxt/typescript-build@0.5.0 12/10/2019

Features

  • Ships and enables the 2 babel plugins required to have Optional Chaining & Nullish Coalescing features working out of the box.

@nuxt/typescript-runtime@0.3.0 12/9/2019

This package has been upgraded to TypeScript 3.7 🚀

Check TypeScript 3.7 Release Notes to know what's new !

The best new features so far : Optional Chaining & Nullish Coalescing 😍

@nuxt/typescript-build@0.4.0 12/9/2019

This package has been upgraded to TypeScript 3.7 🚀

Check TypeScript 3.7 Release Notes to know what's new !

The best new features so far : Optional Chaining & Nullish Coalescing 😍

@nuxt/typescript-build@0.3.0 10/2/2019

Features

  • refactor: migrate codebase to typescript (#135)

@nuxt/types@0.3.0 10/2/2019

Bug Fixes

@nuxt/typescript-runtime@0.4.0 3/2/2020

  • Upgrade TypeScript to 3.8