quasarframework / quasar-testing

Testing Harness App Extensions for the Quasar Framework 2.0+
https://testing.quasar.dev
MIT License
180 stars 65 forks source link

App Transpiling Error: (node:23200) UnhandledPromiseRejectionWarning ForkTsCheckerWebpackPlugin #267

Closed wendellvieira closed 2 years ago

wendellvieira commented 2 years ago

Good afternoon... My project is old, it was created more than a year and a half ago, last week when I went to build the project my pipeline died with this error below. I fixed the "quasar" versions: "1.19.2" and "@quasar/app": "2.3.1" and it worked again. but with that countless other things stopped working.

I would like help to solve the problem below.

thankful

Problem

$ npx quasar dev

Dev mode.......... spa
Pkg quasar........ v1.19.4 Pkg @quasar/app... v2.4.1 Debugging......... enabled

Configured browser support (at least 88.14% of global marketshare): · Chrome for Android >= 103 · Firefox for Android >= 101 · Android >= 103 · Chrome >= 94 · Edge >= 100 · Firefox >= 93 · iOS >= 13.0-13.1 · Opera >= 82 · Safari >= 14

App · Running "@quasar/dotenv" Quasar App Extension... App · Reading quasar.conf.js App · Checking listening address availability (0.0.0.0:8080)... App · Extension(@quasar/dotenv): Extending quasar.conf... App · Transpiling JS (Babel active) (node:23200) UnhandledPromiseRejectionWarning: ValidationError: Invalid configuration object. ForkTsCheckerWebpackPlugin has been initialized using a configurat ion object that does not match the API schema.

(node:23200) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1) (node:23200) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

$ npx quasar info

Operating System - Windows_NT(10.0.19044) - win32/x64 NodeJs - 12.22.8

Global packages NPM - 6.14.15 yarn - 1.22.5 @quasar/cli - 1.3.2 @quasar/icongenie - Not installed cordova - Not installed

Important local packages quasar - 1.19.4 -- Build high-performance VueJS user interfaces (SPA, PWA, SSR, Mobile and Desktop) in record time @quasar/app - 2.4.1 -- Quasar Framework local CLI @quasar/extras - 1.14.2 -- Quasar Framework fonts, icons and animations eslint-plugin-quasar - Not installed vue - 2.7.3 -- Reactive, component-oriented view layer for modern web interfaces. vue-router - 3.5.3 -- Official router for Vue.js 2 vuex - 3.6.2 -- state management for Vue.js electron - Not installed electron-packager - Not installed electron-builder - Not installed @babel/core - 7.18.6 -- Babel compiler core. webpack - 4.44.2 -- Packs CommonJs/AMD modules for the browser. Allows to split your codebase into multiple bundles, which can be loaded on demand. Support loaders to preprocess files, i.e. json, jsx, es7, css, less, ... and your custom stuff. webpack-dev-server - 3.11.3 -- Serves a webpack app. Updates the browser on changes. workbox-webpack-plugin - Not installed register-service-worker - 1.7.2 -- Script for registering service worker, with hooks typescript - 4.2.2 -- TypeScript is a language for application scale JavaScript development @capacitor/core - Not installed @capacitor/cli - Not installed @capacitor/android - Not installed @capacitor/ios - Not installed

Quasar App Extensions @quasar/quasar-app-extension-dotenv - 1.1.0 -- Load .env variables into your quasar project

Networking Host - QWST016 Wi-Fi - 192.168.1.104 vEthernet (Default Switch) - 172.29.96.1 vEthernet (WSL) - 172.18.112.1

wendellvieira commented 2 years ago

hello again gentlemen

I ended up managing to solve the problem by changing some settings in quasar.conf.js

quasar.conf.js

// After
module.exports = configure(function (ctx) {
    return {}
})
// After
extendWebpack(cfg) {}

I came to this conclusion after observing a quasar.config.js from a new project...

I hope this issue helps someone.