N
Nuxt•4mo ago
Artfaith

Error: ForkTsCheckerWebpackPlugin... configuration... does not match the API schema...

Greetings! ✨ I have been trying to upgrade Nuxt v2.14.6 to the latest v2.17.3 for days now.., and it feels like I am almost there! This is the current package.json file: https://dpaste.org/0tVrm. These are the changes: 
-    "dev": "nuxt-ts",
-    "build": "nuxt-ts build --modern=client",
-    "start": "nuxt-ts start --modern=client",
-    "analyze": "nuxt-ts build --modern=client --analyze",
+    "dev": "nuxt",
+    "debug-dev": "NODE_ENV='development' node --inspect='0.0.0.0' -- './node_modules/.bin/nuxt'",
+    "build": "nuxt build --modern=client",
+    "start": "nuxt start --modern=client",
+    "analyze": "nuxt build --modern=client --analyze",
// ...
-    "build:nginx": "ts-node ./commands/build-nginx.js",
-    "build:production": "ts-node ./commands/build-prod.js"
+    "build:nginx": "ts-node ./.project/scripts/build/build-nginx.js",
+    "build:production": "ts-node ./.project/scripts/build/build-prod.js"
// ...
-    "@nuxt/typescript-runtime": "^1.0.0",
// ...
-    "nuxt": "^2.13.3",
+    "nuxt": "^2.17.3",
// ...
-    "@nuxt/typescript-build": "1.0.3",
+    "@nuxt/types": "^2.17.3",
+    "@nuxt/typescript-build": "^3.0.2",
// ...
-    "@nuxtjs/eslint-config-typescript": "^2.0.0",
+    "@nuxtjs/eslint-config-typescript": "^12.1.0",
// ...
-    "@nuxtjs/vuetify": "^2.0.0-beta.2",
+    "@nuxtjs/vuetify": "^1.12.3",
// ...
-    "@types/node": "^14.0.23",
+    "@types/node": "^18",
// ...
-    "eslint": "^7.4.0",
+    "eslint": "^9.1.1",
// ...
-    "eslint-plugin-nuxt": "^1.0.0",
+    "eslint-plugin-nuxt": "^4.0.0",
// ...
-    "node-sass": "^4.14.1",
// ...
-    "sass-loader": "^9.0.2",
+    "sass": "^1.75.0",
+    "sass-loader": "^10",
// ...
-    "vue": "^2.6.11",
+    "typescript": "^5.4.5",
+    "vue": "^2.7.16",
-    "dev": "nuxt-ts",
-    "build": "nuxt-ts build --modern=client",
-    "start": "nuxt-ts start --modern=client",
-    "analyze": "nuxt-ts build --modern=client --analyze",
+    "dev": "nuxt",
+    "debug-dev": "NODE_ENV='development' node --inspect='0.0.0.0' -- './node_modules/.bin/nuxt'",
+    "build": "nuxt build --modern=client",
+    "start": "nuxt start --modern=client",
+    "analyze": "nuxt build --modern=client --analyze",
// ...
-    "build:nginx": "ts-node ./commands/build-nginx.js",
-    "build:production": "ts-node ./commands/build-prod.js"
+    "build:nginx": "ts-node ./.project/scripts/build/build-nginx.js",
+    "build:production": "ts-node ./.project/scripts/build/build-prod.js"
// ...
-    "@nuxt/typescript-runtime": "^1.0.0",
// ...
-    "nuxt": "^2.13.3",
+    "nuxt": "^2.17.3",
// ...
-    "@nuxt/typescript-build": "1.0.3",
+    "@nuxt/types": "^2.17.3",
+    "@nuxt/typescript-build": "^3.0.2",
// ...
-    "@nuxtjs/eslint-config-typescript": "^2.0.0",
+    "@nuxtjs/eslint-config-typescript": "^12.1.0",
// ...
-    "@nuxtjs/vuetify": "^2.0.0-beta.2",
+    "@nuxtjs/vuetify": "^1.12.3",
// ...
-    "@types/node": "^14.0.23",
+    "@types/node": "^18",
// ...
-    "eslint": "^7.4.0",
+    "eslint": "^9.1.1",
// ...
-    "eslint-plugin-nuxt": "^1.0.0",
+    "eslint-plugin-nuxt": "^4.0.0",
// ...
-    "node-sass": "^4.14.1",
// ...
-    "sass-loader": "^9.0.2",
+    "sass": "^1.75.0",
+    "sass-loader": "^10",
// ...
-    "vue": "^2.6.11",
+    "typescript": "^5.4.5",
+    "vue": "^2.7.16",
1 Reply
Artfaith
Artfaith•4mo ago
The error when running npx nuxt: 
ℹ Preparing project for development
ℹ Initial build may take a while
✔ Builder initialized
✔ Nuxt files generated

 ERROR  Invalid configuration object. ForkTsCheckerWebpackPlugin has been initialized using a configuration object that does not match the API schema.
 - configuration has an unknown property 'vue'. These properties are valid:
   object { async?, typescript?, eslint?, formatter?, issue?, logger? }
 - configuration.eslint should be an object:
   object { files, enabled?, memoryLimit?, options?, … }

  - configuration has an unknown property 'vue'. These properties are valid:
  object { async?, typescript?, eslint?, formatter?, issue?, logger? }
  - configuration.eslint should be an object:
  object { files, enabled?, memoryLimit?, options?, … }
  at Object.validate [as default] (node_modules/fork-ts-checker-webpack-plugin/node_modules/schema-utils/dist/validate.js:96:11)
  at new ForkTsCheckerWebpackPlugin (node_modules/fork-ts-checker-webpack-plugin/lib/ForkTsCheckerWebpackPlugin.js:31:31)
  at WebpackBundler.<anonymous> (node_modules/@nuxt/typescript-build/dist/index.js:50:33)
  at next (node_modules/@nuxt/utils/dist/utils.js:506:27)
  at WebpackBundler.<anonymous> (node_modules/@nuxt/utils/dist/utils.js:516:12)
  at WebpackBundler.<anonymous> (node_modules/@nuxt/utils/dist/utils.js:512:29)
  at WebpackBundler.<anonymous> (node_modules/@nuxt/utils/dist/utils.js:512:29)
  at WebpackBundler.<anonymous> (node_modules/@nuxt/utils/dist/utils.js:512:29)
  at WebpackBundler.<anonymous> (node_modules/@nuxt/utils/dist/utils.js:512:29)
  at WebpackBundler.<anonymous> (node_modules/@nuxt/utils/dist/utils.js:512:29)
ℹ Preparing project for development
ℹ Initial build may take a while
✔ Builder initialized
✔ Nuxt files generated

 ERROR  Invalid configuration object. ForkTsCheckerWebpackPlugin has been initialized using a configuration object that does not match the API schema.
 - configuration has an unknown property 'vue'. These properties are valid:
   object { async?, typescript?, eslint?, formatter?, issue?, logger? }
 - configuration.eslint should be an object:
   object { files, enabled?, memoryLimit?, options?, … }

  - configuration has an unknown property 'vue'. These properties are valid:
  object { async?, typescript?, eslint?, formatter?, issue?, logger? }
  - configuration.eslint should be an object:
  object { files, enabled?, memoryLimit?, options?, … }
  at Object.validate [as default] (node_modules/fork-ts-checker-webpack-plugin/node_modules/schema-utils/dist/validate.js:96:11)
  at new ForkTsCheckerWebpackPlugin (node_modules/fork-ts-checker-webpack-plugin/lib/ForkTsCheckerWebpackPlugin.js:31:31)
  at WebpackBundler.<anonymous> (node_modules/@nuxt/typescript-build/dist/index.js:50:33)
  at next (node_modules/@nuxt/utils/dist/utils.js:506:27)
  at WebpackBundler.<anonymous> (node_modules/@nuxt/utils/dist/utils.js:516:12)
  at WebpackBundler.<anonymous> (node_modules/@nuxt/utils/dist/utils.js:512:29)
  at WebpackBundler.<anonymous> (node_modules/@nuxt/utils/dist/utils.js:512:29)
  at WebpackBundler.<anonymous> (node_modules/@nuxt/utils/dist/utils.js:512:29)
  at WebpackBundler.<anonymous> (node_modules/@nuxt/utils/dist/utils.js:512:29)
  at WebpackBundler.<anonymous> (node_modules/@nuxt/utils/dist/utils.js:512:29)
What might it be? Is fork-ts-checker-webpack-plugin still required even? This project was not started by me, and I am not sure Webpack was even used and is required. The main reason I am doing all of this is to try to update Vue 2.6.12 of Nuxt 2 to the last Vue 2 -> 2.7.16 (alongside Nuxt 2). And, currently, am... probably almost there since at least Yarn successfully installs the package.json without the lock file in completely clear environment with: - Nuxt v2.17.3 (dep); - Vue v2.17.16 (dev-dep). I see... It must be something with package version mismatch/incompatibility since with current packages installed using Yarn, found the package mentioned stated in node_modules/@nuxt/typescript-build/dist/index.js: 
if (options.typeCheck && isClient && !isModern) {
  // ...
  const ForkTsCheckerWebpackPlugin = require('fork-ts-checker-webpack-plugin');
  // ...
  config.plugins.push(new ForkTsCheckerWebpackPlugin((0, defu_1.defu)(options.typeCheck, {
  // ...
if (options.typeCheck && isClient && !isModern) {
  // ...
  const ForkTsCheckerWebpackPlugin = require('fork-ts-checker-webpack-plugin');
  // ...
  config.plugins.push(new ForkTsCheckerWebpackPlugin((0, defu_1.defu)(options.typeCheck, {
  // ...
Want results from more Discord servers?
Add your server
More Posts
useAsyncData works only on reloadI know i am probably missing something trivial, or worse i didn't understand at all nuxt. In my nuxWhat's the trick to dev/build from nuxt content package fetch from github?Hi. due to a bug inside the version I was using, I need to be on the really latest update so I modiPlugins - add third party plugin to NuxtHello, I would like to add fast-json-patch into Nuxt as plugin. I want it to be auto-imported and aPartytown with Vercel Analystics & Vercel Speed InsightsHow to integrate vercel analytics & vercel speed insights ith partytown in nuxt? Could not find any Partytown with plausible analysticsHi guys, i followed the instructions posted here on examples: https://nuxt.com/modules/partytown#pDynamic nested pagesIs there a way to have a route structure where there is an unknown amount of slugs eg: ``` example 1Create global instance of ofetchI want to create a global ofetch instance, on which I can add custom header and I want it to be presnuxt generate sets process.env.NODE_ENV to prerender after nuxt.config.tsWhen i run nuxt generate and i print the process.env.NODE_ENV in the nuxt.config.ts it is as expecteUForm schema arrayHello, I need to create an extensible form for my project I'm using zod, which looks like this (no Any guideline on using Lit based web components in Nuxt project?I'm new to Nuxt, just started to use today. I've some webcomponents coming from node_modules and som