Erick Zhao

Sorry for waffling about by transferring this issue across repos over and over again. I took a closer look at what needs to be done to fix this (because Node...

Hey @entropy-ibex, I seem to be able to repro the same issue. This might be an upstream problem with `ts-node`: https://github.com/TypeStrong/ts-node/discussions/1867

@brianlyn thanks for pointing that out!

Hi @guidupuy, do you have a more specific repro case? I don't think ESLint comes included when you initialize a new Forge app.

FWIW I think this should be fixed if you upgrade your system Node.js to 22.13 or above, but you will run into DEP0174 due to some legacy Electron Packager code:...

Hey @danikaze, Out of the box, you would generally want to route your `ipcRenderer` calls via the preload script: https://www.electronjs.org/docs/latest/tutorial/ipc In theory, the renderer is able to execute modules available...

Yeah, I think it makes sense to support it as well. The pnpm work in #3822 unblocked alternative package managers that aren't yarn or npm.

Hey @youaresoyoung, that's a great point. I think it'd be good to actually integrate this as part of the `init` API so that pnpm projects initialized with Electron Forge work...

Hey @hab25, I think this is a pretty good point. I'll try to take a look when I have the time next week.

ref https://github.com/electron/forge/issues/3662 i think this is a problem on the `npm` side but the documentation indeed needs to be updated: https://github.com/npm/cli/issues/3136 From https://github.com/electron/forge/issues/3662#issuecomment-2266291311, it seems like alternate syntaxes work.