Vite Plugin with ESM support for main about forge

[jrj2211]

I found that I can override that setting in vite.main.config.js:

// https://vitejs.dev/config
export default defineConfig({
  resolve: {
    ...
  },
  build: {
    lib: {
      formats: ["es"],
    },
  },
});

I have another issue now though, as in esm __dirname is not available. This is needed to specify the index.html path and the preload file. I changed it to:

const __dirname = url.fileURLToPath(new URL(".", import.meta.url));
...
mainWindow.loadFile(path.join(dirname, "index.html"));

However, Vite replaces import.meta.url with self.location and then Vite errors out ReferenceError: self is not defined.

If I replace them with relative paths, it loads the files but warns it wants an absolute path for preload.js.

Guessing some sort of MAIN_WINDOW_PRELOAD_VITE_ENTRY and MAIN_WINDOW_VITE_ENTRY will need to be generated outside of Vite similar to how the webpack plugin works?

[Sahasrara]

The combination of svelte + vite + electron + forge doesn't seem to work unless we have ESM support.

[jrj2211]

Aweome! I haven't had a chance to try your suggestion but I'm starting a new project tomorrow and might mess around with it more. Hopefully the official support comes soon but good to know its coming by default soon!

[sparecycles]

+1.

Thanks for your investigation!

I wonder if you tried import.meta.resolve(...)? It's both more to the point and perhaps vite doesn't try to mess with it?

I'm brought here trying to use both @sveltejs/vite-plugin-svelte which is esm-only, (and so it requires "type": "module" in package.json), and this is tripping me up.

I think I can slap an dist-electron/package.json in with { "type": "commonjs" } as a work-around but it feels a bit horrid. 😉

[caoxiemeihao]

The combination of svelte + vite + electron + forge doesn't seem to work unless we have ESM support.

You can try to this 👉 #3309

The next version of Vite plugin will be use "type"="module" by default, coming soon...

[Sahasrara]

Is this something that's planned? I'm hoping to use Forge with Svelte + Vite (not SvelteKit).

[sparecycles]

The "horrid" workaround I suggested seems to be working for me. I've got vite+forge+tailwind+typescript+svelte+melt+workers+import("node:module").register (node20, electron29-alpha) working fine.