eslint-plugin-vue | Eslint plugin for vue components | Plugin library

I need help debugging Webpack's Compression Plugin.

SUMMARY OF PROBLEM

• Goal is to enable asset compression and reduce my app's bundle size. Using the Brotli algorithm as the default, and gzip as a fallback for unsupported browsers.
• I expected a content-encoding field within an asset's Response Headers. Instead, they're loaded without the field. I used the Chrome dev tools' network tab to confirm this. For context, see the following snippet:
• No errors show in my browser or IDE when running locally.

WHAT I TRIED

• Using different implementations for the compression plugin. See below list of approaches:
  1. (With Webpack Chain API)

I am attempting to deploy a vuejs app to github pages. I have followed every stackoverflow post, and every tutorial I have found online. No matter what I do, the page only displays the readme file.

github repo github page

I am using the gh-pages branch.

package.json:

I am working on Vue 3 application I am using SVG code as a background URL in sass.

in my nuxt app , after changing route using this.$router.push({ path: '/path' }) i got the nodeOps.tagName(...) is undefined in firefox , in chrome i get cannot get access to .toLowerCase() of undefined in the same line .

it happens in createPatchFunction of vue.runtime.esm.js versions: nuxt:^2.14.12, vue:^2.6.12

I am working on project upgrade from Vue 2 to Vue 3. The code base changed according to Vue migration documents: https://v3.vuejs.org/guide/migration/introduction.html#overview. I have mismatch of above mentioned libraries. Does somebody has a running project and would share their working library versions

Current mismatch error is :

After updating my npm packages, some of the imports from the 'vue' module started showing errors:

TS2305: Module '"../../node_modules/vue/dist/vue"' has no exported member 'X'

where X is nextTick, onMounted, ref, watch etc. When serving the project, Vue says it's "failed to compile". WebStorm actually recognizes the exports, suggests them and shows types, but the error is shown regardless. Some exports like computed and defineComponent work just fine.

What I've tried:

• Rollback to the previously used Vue version "3.2.2" > "3.0.11". It makes the abovementioned type errors disappear, but the app stops working entirely, showing lots of TypeError: Object(...) is not a function errors in console and not rendering the app at all. In the terminal, some new warnings are introduced: "export 'X' (imported as '_X') was not found in 'vue' where X is createElementBlock, createElementVNode, normalizeClass and normalizeStyle.
• Rollback other dependencies. None of the ones that I tried helped fix the problem, unfortunately.
• Manually declare the entirety of 'vue' module. We can declare the 'vue' module exports in shims-vue.d.ts, and it actually makes the errors disappear, however, this seems like a terrible, time-consuming workaround, so I would opt out for a better solution if possible.

My full list of dependencies:

I create project using vue-cli and install vuetify using vue-cli. I create a folder called sass in my src directory with a file named variables.scss.

Documentation says (https://vuetifyjs.com/en/features/sass-variables/):

The vuetify-loader will automatically bootstrap your variables into Vue CLI’s compilation process, overwriting the framework defaults.

My files:

src\plugins\vuetify.js

The app has been running successfully in production for a year, and works perfectly on MacOS localhost. Recently needed to set up the app to run on Windows 10 localhost, and after resolving all the errors, now the app boots up, requests seem to get through, however, only the '/' page actually renders, all the other routes don't render and stay at a blank page.

What could be a reason?

During initial setup, I ran into an issue with windows-build-tools and a missing Python, which I ended up eventually resolving by installing everything through Chocolatey. Could this be related?

Node version on Windows is newer than one specified in project, could this cause this?

I'm happy to provide more details and perform any experiments any of you recommend or suggest. My own guess is that it is either something related to setup on Windows or some issue with the packages on Windows.

The app is booted up through a package.json start script:

I have some img tag which I fill it with dynamic address with require, it works as expected in the component but when I write a test for it throws this error