Artfaith
Artfaith
PostsComments
NNuxt
Created by Artfaith on 4/28/2024 in #❓・help
Silence SASS deprecation warnings
Interesting... I added the following Yarn resolution to package.json 
"resolutions": {
  "@nuxtjs/vuetify@2.0.0-beta.2/sass": "~1.32"
}
"resolutions": {
  "@nuxtjs/vuetify@2.0.0-beta.2/sass": "~1.32"
}
Removed node_modules and yarn.lock, and with yarn install, it still returns the same SASS version 1.75.0 for Vuetify, but the required is ~1.32. What might it be?
6 replies
NNuxt
Created by Artfaith on 4/28/2024 in #❓・help
Silence SASS deprecation warnings
I'll try setting a Yarn resolution for Vuetify to SASS ~1.32.
6 replies
NNuxt
Created by Artfaith on 4/28/2024 in #❓・help
Silence SASS deprecation warnings
I see... 
$ yarn list --pattern 'sass'
yarn list v1.22.19
├─ @nuxtjs/vuetify@2.0.0-beta.2
│  ├─ sass-loader@8.0.2
│  └─ sass@1.75.0
├─ @types/node-sass@4.11.7
├─ postcss-sass@0.4.4
├─ sass-loader@10.5.2
├─ sass@1.32.13
└─ stylelint-config-rational-order@0.1.2
   └─ postcss-sass@0.3.5
Done in 0.69s.
$ yarn list --pattern 'sass'
yarn list v1.22.19
├─ @nuxtjs/vuetify@2.0.0-beta.2
│  ├─ sass-loader@8.0.2
│  └─ sass@1.75.0
├─ @types/node-sass@4.11.7
├─ postcss-sass@0.4.4
├─ sass-loader@10.5.2
├─ sass@1.32.13
└─ stylelint-config-rational-order@0.1.2
   └─ postcss-sass@0.3.5
Done in 0.69s.
6 replies
NNuxt
Created by Artfaith on 4/28/2024 in #❓・help
Silence SASS deprecation warnings
Since this change is SASS v1.33, I have installed "sass": "~1.32" as also suggested in the mentioned GitHub issue comment, but am still getting the warnings...
6 replies
NNuxt
Created by Artfaith on 4/28/2024 in #❓・help
Silence SASS deprecation warnings
I know those are quite outdated, but... it's been days since I am trying to update this project not started by me am being mostly in back-end even (still learning ineffably marvelous Nuxt, Vue...)... I am not sure how much time will it require, and hence am trying to update it step by step.
6 replies
NNuxt
Created by Artfaith on 4/26/2024 in #❓・help
Error: ForkTsCheckerWebpackPlugin... configuration... does not match the API schema...
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, {
  // ...
6 replies
NNuxt
Created by Artfaith on 4/26/2024 in #❓・help
Error: ForkTsCheckerWebpackPlugin... configuration... does not match the API schema...
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).
6 replies
NNuxt
Created by Artfaith on 4/26/2024 in #❓・help
Error: ForkTsCheckerWebpackPlugin... configuration... does not match the API schema...
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).
6 replies
NNuxt
Created by Artfaith on 4/26/2024 in #❓・help
Error: ForkTsCheckerWebpackPlugin... configuration... does not match the API schema...
This project was not started by me, and I am not sure Webpack was even used and is required.
6 replies
NNuxt
Created by Artfaith on 4/26/2024 in #❓・help
Error: ForkTsCheckerWebpackPlugin... configuration... does not match the API schema...
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?
6 replies