Vite support

[RobbieTheWagner]

@bendemboski do you know if we could use something like https://electron-vite.org/ to setup vite support here or what do you think the future is for this addon?

[bendemboski]

I'm not sure, I haven't gotten our app close enough to using vite to be able to really dig in. However, I very much hope that it's possible to find some kind of unification here.

I haven't tried electron-vite, but I have been using Electron Forge's vite plugin (in conjunction with ember-electron) for some time, just to build & bundle the main process & preload scripts. For some time now I've thought ember-electron's architecture is kinda backwards -- all the Electron tooling wants the Electron project to "host" the renderer project, not the other way around (like ember-electron does).

With vite support in Ember/embroider, I would very much hope that it would just plugin right into something like electron-vite or forge's vite plugin, maybe with some kind of Ember-specific vite plugin if needed, but I'd really hope that wouldn't be needed.

I don't know when I'll have time, but at some point I'd love to try setting up an electron-vite or forge/vite project with a vite-based Ember app in the same project and see what happens...it should theoretically work after some amount of blood, sweat, and tears...

[RobbieTheWagner]

@bendemboski gotcha, I know very little about the setup here, but would definitely be interested in helping out if I can.

[bendemboski]

@RobbieTheWagner if you wanna try digging in, I'd love to provide help/support from the Electron side. I have almost no experience with Ember/vite yet, but quite a bit with @electron/forge's vite template/plugin.

What I'd probably start with is running npx create-electron-app@latest my-new-app --template=vite-typescript to create an @electron/forge project set up with vite/typescript. The vanilla project isn't too hard to find your way around:

• forge.config.ts feeds forge's Vite plugin a simple config telling it what to build (main process, preload script, renderer process)
• vite.renderer.config.ts is the vite config for the renderer process, which starts out pretty empty (although the plugin sets up some defaults
• src/main.ts is the main process code that loads up index.html
• index.html is the renderer HTML

So the approach I'd try is to "merge" this with a blueprint-generated Ember/vite app, where Ember's vite config gets put into vite.renderer.config.ts, and then index.html is replaced with Ember's index.html which is the entrypoint to the whole Ember app. I'm sure it's more complicated and there are stumbling blocks, but on the surface it seems like these two things should be able to fit together...

[RobbieTheWagner]

Thanks for the details @bendemboski! I will give this a try in the coming days/weeks.

[RobbieTheWagner]

@bendemboski what did you do with handle-file-urls in the vite setup? I am working on converting everything to TS and ESM and not sure what to do there.