Implement how to serve two windows

[kuworking]

It is not possible (is it? I've been trying for a while now and have concluded it is not) to serve two different directories when the electron app has two windows.

Something like this

const loadURLOne = serve({ directory: 'one' })
const loadURLTwo = serve({ directory: 'two' })

function createWindow() {
  const oneWindow = new BrowserWindow({
    width: 1800,
    height: 1600,
  })

  const twoWindow = new BrowserWindow({
    width: 1800,
    height: 1600,
  })

  if (isDev) {
    oneWindow.loadURL('http://localhost:3000/one')
    twoWindow.loadURL('http://localhost:3000/two')
  } else {
    loadURLOne(oneWindow)
    loadURLTwo(twoWindow)
  }

This in dev works as expected (the localhost is an astro site)
But in build I can only get two windows opened that point to the same directory (the first one).

So this would be a nice feature to have in mind, if it is feasible.

EDIT: Or a variant would be to point, instead of a directory, to a file

const loadURLOne = serve({ directory: '.', file: 'index.html' })
const loadURLTwo = serve({ directory: '.', file: 'two.html' })

[hadeeb]

You can use the scheme option to create 2 different roots.

const loadURLOne = serve({ directory: 'one', scheme: 'app' })
const loadURLTwo = serve({ directory: 'two', scheme: 'foo' })

[kuworking]

It sort of works, but not being able to point to a file but to a folder, I get all my css lost. I would need to search them at a ../ level, but that is too messy since the folder exists at build level, but not at dev level where the css are imported within a react component. This destroys the dev experience.

So I'll keep it only working at dev level (this is an app for me anyway), but it would be great that the serve would allow to pinpoint to a specific file instead of a folder.

(Thanks!)

[mhkeller]

See if this works for you: https://github.com/mhkeller/electron-serve/tree/custom-route

That's a branch that supports a route option. It defaults to index but you can set it to foo and it will load foo.html.

There's also a branch called query-params which supports passing those in when you call the returned function with a given window.

The main branch of my fork has both changes merged. I can put these in a PR and see if either is of interest.

[mhkeller]

It may be possible to close this now that custom HTML file names are supported via #36

[mhkeller]

Since version 1.3.0, this works for me as long as I set a different schema (my files are all in the same directory).