The main change is basically to use webpack serve instead of webpack-dev-server (god knows why they changed that, because you still need webpack-dev-server) but with existing projects I've got mixed results. For minimal/new Fable projects it's usually trivial. unfortunately not as straightforward as it should be. It might help to put this on the documentation somewhere? Unless this has been done and I'm missing something.
#FABLE 3 FREE ACCIDENT HOW TO#
On this topic - every time I try to debug fable 3 source maps (which work intermittently on my current electron build) my documentation for how to do this is a tangled set of googled posts. It would be really helpful to have a complete description of fable 3 output - since I'm hoping this is pretty simple now? Is this going to be a big mess? Who has working fable 3 / elmish/ webpack 5 boilerplate? I am also half-thinking I should try to use vite as bundler with vite/electron/react starting point but that looks riskier to me. I see more trouble getting HMR to work with Elmish but with any luck HMR working with React in an existing boilerplate would be a good start? So I'm wondering - what else will I need to consider (source maps are always an issue)? electron-webpack - currently used - does not work (and will not work) with later versions of electron so I will start with a well maintained electron-react-webpack 5 boilerplate or (one of these is minimal - I could build up as needed, the other enormous) and then getting this to work with Fable/Elmish.ĪFAIK Fable 3's main interaction with Webpack is the output js files which are all picked up from the top-level entry and should be trouble-free. I'm thinking of changing my boilerplate for current fable 3/elmish/hmr/webpack 4/electron (using electron-webpack) to webpack 5.
0 kommentar(er)
