Has fable 3/elmish/react been made to work with webpack 5 or vitejs yet? Nagareyama build documentation
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- electron, fsharp, react, vite, webpack
- Domain
- build-system, desktop-dev, documentation
Research direction
Start by comparing the two linked electron-react-webpack-boilerplate package.json files and the electron-vite-react starting point. Determine which Fable 3/Elmish setup and source-map behavior can be documented, then make the supported webpack 5 or Vite workflow and debugging steps explicit.
Written by the indexing model from the issue text.
Description
Fable 3
I'm thinking of changing my boilerplate for current fable 3/elmish/hmr/webpack 4/electron (using electron-webpack) to webpack 5. 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 https://github.com/alexdevero/electron-react-webpack-boilerplate/blob/master/package.json or https://github.com/electron-react-boilerplate/electron-react-boilerplate/blob/main/package.json (one of these is minimal - I could build up as needed, the other enormous) and then getting this to work with Fable/Elmish.
AFAIK 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 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)?
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 https://github.com/twstyled/electron-vite-react but that looks riskier to me. It would be really helpful to have a complete description of fable 3 output - since I'm hoping this is pretty simple now?
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 might help to put this on the documentation somewhere? Unless this has been done and I'm missing something.
- Dominant language
- F#
- Stars
- 46
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Getting set up
We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from fable-compiler/fable3-samples
-
Difficulty 2/5 1-3 hours Newbie friendliness 48/100
fable-compiler/fable3-samples#11 · 3 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
fable-compiler/fable3-samples#2 · 13 comments ·
All issues in fable-compiler/fable3-samples
Similar issues
-
package-update
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug p:1-highest pydanty:bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
pydantic/pydantic-ai#8841 · 1 comment ·
Maintainers usually reply within 1 day
-
bug good first issue
Difficulty 1/5 Under an hour Newbie friendliness 88/100
yunaremaia/diff-contract#79 ·
-
self-care self-care:docs-build-time-investigator
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
githubnext/gh-aw-cao#14184 ·
Maintainers usually reply within 1 day
-
backlog
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day