Erick Zhao

Good point. @MarshallOfSound of sound had a WIP PR for webpack a while back: https://github.com/electron/forge/pull/3511 Added to the v8 milestone.

@RareScrap `nodenext` is a moving target so I'd prefer to avoid it but yeah definitely moving away from the current tsconfig settings.

This sounds like an issue with renderer sandboxing in Electron 22, which is where the `undefined` in that path is coming from. You can get past that with `sandbox: false`...

Currently using `@sentry/electron` in some of the Forge apps I maintain, but I think we might be a few major versions behind. Let me upgrade and see if I can...

Hey @wwwillchen, thanks for the report. Based on the logs, this seems to be failing at the Vite build step before packaging starts. I'll update the issue title accordingly. Did...

Yeah, I can see how it's pretty poor UX. I'm surprised it didn't fail, either. BTW, if you're building in CI, you can use the `--dry-run` and `--from-dry-run` flags to...

Hey @wwwillchen, I don't have an update on the exit code issue, but the next version of Electron Forge will allow you to set a max concurrency limit for Vite...

We specifically monkeypatch that package to work with Electron Forge. Is there a reason you want to install 1.10.0?

Hey @steveoh, the next major version of Electron Forge will update all dependencies to the latest. We've pretty much completed this work for all dependent packages in Forge: https://www.electronjs.org/blog/ecosystem-node-22

@steveoh I've kicked off a `next` branch for incoming work and currently planning on starting beta releases before the end of the month, after we've finished related npm publishing work...