How can i pack my app like forge do, but for electron-builder?

[meager shell]

I am wondering i can webpack my app like i have in forge, but for electron-builder?

this is my script i built for electron-builder:

"dev": "cross-env NODE_ENV=development yarn build:webpack --watch && yarn start-electron",
"start-electron": "electron ./dist/main.js",
"build:webpack": "yarn build:main && yarn build:renderer && yarn build:preload",
"build:main": "webpack --config webpack.builder.main.config.ts",
"build:renderer": "webpack --config webpack.builder.renderer.config.ts",
"build:preload": "webpack --config webpack.builder.preload.config.ts",

this is the script for forge:
"start": "cross-env NODE_ENV=development ELECTRON_FORGE_START=true electron-forge start",

[vague ferry]

Alright, so what don't work currently?

[meager shell]

in forge the webpack generate those const:
declare const MAIN_WINDOW_WEBPACK_ENTRY: string
declare const MAIN_WINDOW_PRELOAD_WEBPACK_ENTRY: string

in builder i have no idea how to create similarity

What i really want to do is to be able to build and create packages for windows with nsis and auto-update

[vague ferry]

what are these const used for?

[meager shell]

i could maybe staying the forge for webpack? and just do the build process with electron-builder somehow?

[vague ferry]

I can't see any advantage at keeping Forge if in the end you use builder to package 🤷‍♀️

[meager shell]

yes that what i thnink also

https://www.electronforge.io/config/plugins/webpack

Those string are written there:
They supply the relative path for preload and main_window entry

[vague ferry]

In the build folder, after you run build:webpack, what path your main.js uses to display the window content and preload?

[meager shell]

this is after using build:webpack

i think i may have missing the main_window folder

[vague ferry]

what's in main.js?

[meager shell]

in forge webpack folder i have it:

[vague ferry]

don't worry about the folder