IlyaSemenov/nuxt-vite-legacy

Issue with Loading JavaScript in Nuxt 3 App on Chromium 49

Closed this issue · 6 comments

Hi there,

I've been trying to use your plugin for my personal project, as it is necessary for my Nuxt 3 app to work under Chrome 49. I downloaded Chromium version 49 (Version 49.0.2623.23 (64-bit)) for this purpose. I attempted to launch the playground in the repository using this version, but the JavaScript files are not loading. This issue occurs both in dev mode and build mode. Any insights into what might be causing this problem?

Thanks!

Chromium 49:
image

Current Chrome:
image

You're trying it in dev mode, where it's not supposed to work. If you run the steps outlined in "Development and Testing" section verbatim, it will work (more or less so):

image

Hi Ilya,

I tried it anyway, but the following error occurs in the browser and the page does not loading.
OS: Windows 11, Chromium 49

image

Do you have any ideas for this?

No, not a clue. This probably has something to do with Chromium itself. Can it load anything else?

I have a relatively extensive SaaS (100+ heavily scripted pages) which runs fine on Windows XP / Chrome 49 clients with this module. These are however actual native Google Chromes (same as on my screenshot above), not Chromium builds.

I have a Set-top-box, and there runs Chrome 49 engine, I wanted to try, but I couldn't generate production (npm run generate), because there was an error:
Nuxt Build Error: [vite]: Rollup failed to resolve import "mdn-polyfills/Element.prototype.getAttributeNames" from "vite/legacy-polyfills".
This is most likely unintended because it can break your application at runtime.
If you do want to externalize this module explicitly add it to
build.rollupOptions.external

This is most likely unintended because it can break your application at runtime.
If you do want to externalize this module explicitly add it to
build.rollupOptions.external

This is a single start project from nuxt 3 (npx nuxi@latest init text-legacy), and I added your plugin for this project.

Do you have any idea from that?

It looks like you didn't install the polyfill that you intended to use.

Run:

npm i --save-dev mdn-polyfills

Closing due to lack of feedback, and probably a non-problem.