Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Fable 3 nodejsbundle sample upgrade

Open
#2 13 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
nodejs, webpack

Research direction

Start with the nodejsbundle sample and its webpack.config.js, then compare how Fable-loader and the dotnet fable tool are referenced. Check the existing Fable 2 migration guide for the expected documentation structure. Done means the sample's Fable 3 setup is updated and the relevant migration guidance is available.

Written by the indexing model from the issue text.

Description

I've started looking into nodejsbundle sample, and stumbled into several problems / questions:

  1. Fable-loader doesn't seem to be updated for Fable 3, should it be used at all ?
  2. Should we use 'dotnet fable' tool ?
  3. I didn't find 'Migration to Fable 3' guide on the website, however there is such a guide for Fable 2 (Migrating to Fable 2)
    Such a guide would be very helpful to update webpack.config.js specifically
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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from fable-compiler/fable3-samples

All issues in fable-compiler/fable3-samples

Similar issues

More Build System issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.