truumahn

Do I understand correctly that this issue doesn't break IE, just doesn't work with it? In that case I'd think the plugin can be used with mixed browsers from the...

> And it happens with vite-plugin-ssr + react too. Only because you imported the images, not used them with the root path as `/logo.svg` directly at the `src` attribute of...

It builds successfully with the following `vite.config.ts`: ```ts import vue from "@vitejs/plugin-vue"; import ssr from "vite-plugin-ssr/plugin"; import { UserConfig } from "vite"; const config: UserConfig = { plugins: [ vue({...

I'm closing this as the original issue has been resolved. The discussion can be continued in https://github.com/vitejs/vite/discussions/10097

Hi! I just encountered the same issue. Although the workaround is welcome, it would be great if this was working out of the box. I haven't started checking the code...

For prerendering with sitemaps, I did the following workaround, using `sitemap.js`: I created a `prerender.ts` file: ```ts import { prerender } from 'vite-plugin-ssr/cli'; import { SitemapStream, streamToPromise } from 'sitemap';...

Thank you for your work @CodeVoyager, would be great to get this fix rolling because enabling i18n practically breaks the Navigation plugin currently.

As a fellow Hungarian I commend your work here @popovicsandras! I certainly hope this PR will soon gain traction among the maintainers.

I'm not sure how how you got to that error message, I just cloned the repo, ran `npm install` then `ember serve`. I did get an entirely different error though...

@mansona have you had a chance to look at this since then?