Tofandel
commented
1 week ago The plugin is not built specifically for vite it on purpose only uses rollup hooks, from what I see the @vitejs/plugin-legacy is using the transformIndexHtml vite hook and seems to write multiple index.html in the output which might be what is causing an issue
I'll need to look into it but don't have any capacity to do so until November, maybe I can also use a custom transformIndexHtml hook in the case of vite to retrieve the content of the index.html file instead of looking on the filesystem.
yuanman0109
My project is based on Vite packaging. Since my previous project was SPA, I ultimately hope that my project can be converted to SSG. Therefore, I started running
npm install - save dev @ perenderer/rollup-plugin @ perenderer/renderer puppeteer puppeteer, and addedimport pre render from '@ perenderer/rollup-pluginin Vite. config. ts, with the following configuration:But when I run vite build, the following error occurs:
My index.html file is located in the project root directory, at the same level as vite.config.js. Why can't find it? After changing the headless in rendererOptions to false, I found that Chrome returned 500 when accessing 127.0.0.1:8000. I don't know why running @ pererenderer/rollup plugin doesn't allow me to access my static resources. If I remove the plugin and run vite build again, there is an index.html file in my dist directory... ... ... After a period of investigation, I finally pinpointed the issue to a plugin. If I were to introduce this plugin, the build would encounter errors. If I were to remove it, the build would proceed normally. I am not sure why this plugin has such problems, the plugin: '@vitejs/plugin-legacy': 4.1.1_terser@5.21.0+vite@4.4.11