Building Leo-Web locally

[Viktor Ransmayr]

Hello Félix,

I followed your description in CONTRIBUTING.md - and - I am able to build & run the app fine in a Debian & a Fedora container. - Thanks a lot for that !

One small thing, that I noticed, is that whenever I try to perform a subsequent 'git pull' operation to update my local clone, I have to first 'git stash' local changes (See Log-001).

If I read the logs correctly, these changes are made every time the development server is started (See Log-002).

Is this the accepted & intended way - or - am I missing something ?

Viktor

### Log-001

    📦[user@leo-web-on-fedora ~]$
    📦[user@leo-web-on-fedora ~]$ cd projects/leo-web/
    📦[user@leo-web-on-fedora leo-web]$
    📦[user@leo-web-on-fedora leo-web]$ git branch
    * master
    📦[user@leo-web-on-fedora leo-web]$
    📦[user@leo-web-on-fedora leo-web]$ git pull
    remote: Enumerating objects: 971, done.
    remote: Counting objects: 100% (197/197), done.
    remote: Compressing objects: 100% (114/114), done.
    remote: Total 971 (delta 88), reused 83 (delta 83), pack-reused 774 (from 2)
    Receiving objects: 100% (971/971), 7.11 MiB | 1.50 MiB/s, done.
    Resolving deltas: 100% (550/550), completed with 21 local objects.
    From https://github.com/boltex/leo-web
       f2ad259..46d5bef  master              -> origin/master
       6a1f02a..09ab352  devel               -> origin/devel
     * [new branch]      felix-custom-themes -> origin/felix-custom-themes
    Updating f2ad259..46d5bef
    error: Your local changes to the following files would be overwritten by merge:
            package.json
    Please commit your changes or stash them before you merge.
    Aborting
    📦[user@leo-web-on-fedora leo-web]$

### Log-002

    📦[user@leo-web-on-fedora leo-web]$
    📦[user@leo-web-on-fedora leo-web]$ npm run dev

    > leo...@1.0.37 dev
    > webpack serve --mode=development

    isProd false
        [webpack-cli] Compiler starting...
        [webpack-cli] Compiler is using config: '/home/user/distroboxes/projects/leo-web-on-fedora/projects/leo-web/webpack.config.js'
    Executing onWatchRun build scripts
    Webpack onWatchRun
    Running prepare.js
    Added git info in package.json
    Executing pre-build scripts
    Webpack onBuildStart
    Running prepare.js
    Added git info in package.json
    <i> [webpack-dev-server] Project is running at:
    <i> [webpack-dev-server] Loopback: http://localhost:8080/, http://[::1]:8080/
    <i> [webpack-dev-server] On Your Network (IPv4): http://10.137.0.29:8080/
    <i> [webpack-dev-server] Content not from webpack is served from './dist' directory
        [webpack-cli] Compiler finished
        [webpack-dev-middleware] Compilation finished
    ... 

[Thomas Passin]

Git doesn't let you step on your local changes when you pull an update (unless you force it to). After the update you would re-apply your changes from the stash. The best way to handle this situation is to do all your local work on your own branch, and update it from the remote devel branch (or whatever it's called for Leo-Web) from time to time.

[Viktor Ransmayr]

Hello Thomas,

tbp1...@gmail.com schrieb am Dienstag, 7. Juli 2026 um 16:00:51 UTC+2:

Git doesn't let you step on your local changes when you pull an update (unless you force it to). After the update you would re-apply your changes from the stash. The best way to handle this situation is to do all your local work on your own branch, and update it from the remote devel branch (or whatever it's called for Leo-Web) from time to time.

I did not make any local changes to the 'package.json' file ...

They were done by the 'webpack-cli'  (See Log-002).

[Félix]

Yeah - oops! I should have documented that part of the software 'compilation' build phase: I add a little something to the package.json at build time, it gets imported by the program at run time to be able to display that part at startup in the log pane:


It's not required to run smoothly (will silently omit the git branch and hash if absent from the package.json at runtime)

When I commit, I always remove it beforehand... 

I guess I should only add this when running a production build. Or I should have at the very least document it in the CONTRIBUTING.md file!! 

Many thanks to Viktor to shed some light on this!  I created issue 51 on the github's project page so I dont forget to address this.

Félix

[Viktor Ransmayr]

Hello Félix,

Am Mi., 8. Juli 2026 um 02:51 Uhr schrieb Félix <felix...@gmail.com>:

Yeah - oops! I should have documented that part of the software 'compilation' build phase: I add a little something to the package.json at build time, it gets imported by the program at run time to be able to display that part at startup in the log pane:



It's not required to run smoothly (will silently omit the git branch and hash if absent from the package.json at runtime)

When I commit, I always remove it beforehand... 

Thanks for your clarification & the ticket creation !

Viktor