No internet connection
  1. Home
  2. DEVELOPMENT

Claude Code - working on Nexus and a way to use HTML as the Viewer of Event Modeling

By @IvanTheGeek
    2026-03-14 11:15:25.069Z

    When creating prompts in Claude Code to develop the idea that the Event Model can be done in HTML, I wanted a place to create the prompt that

    1. preserves my prompt for history
    2. is not lost if the UI crashes or resets
      • this has happened several times where a long prompt ends up getting lost before submitting in various AI UIs.
    3. can be cross-linked when the AI raw chat data log is ingested and used for training and analysis.
    • 5 replies
    1. I
      @IvanTheGeek
        2026-03-14 11:22:58.608Z

        Commit to experiment branch any changes not committed
        then Create a new branch from experiment branch named "wasm-only"
        modify the app so that it can be ran completely as a WebAssembly app. The idea is to produce an artifact set that can be uploaded to a static web hosting site and me or any user can hit the url, the app downloads to the browser and can be fully used off line. Do not add PWA functionality yet. That will be a different attempt.
        When done, make a commit in wasm-only branch.

        Using Claude Code Windows Desktop, Opus 4.6

        As a note, this actually happened exactly at this time. I pasted the prompt, Claude Code told me my session had expired and I lost access to the prompt because i had to restart Claude app!

        1. I@IvanTheGeek
            2026-03-14 11:33:47.545Z2026-03-14 11:42:12.036Z

            after seeing the result. I have decided that I need to re-branch and do an updated prompt.


            revert back to latest experiment branch commit then create a new branch called "wasm-added" and then

            modify the app so that it can be ran completely as a WebAssembly app as an option. The idea is to produce an artifact set that can be uploaded to a static web hosting site and me or any user can hit the url, the app downloads to the browser and can be fully used off line. The option to run the app as it now and the option to run it as wasm only and a wasm with server backend remote is desired.
            So the goal is WASM only OR WASM + server OR Server

            Do not add PWA functionality yet. That will be a different attempt.

            create a MD doc that explains how to get the different ways of hosting and running in a docs directory that will be committed.

            When done, make a commit in wasm-only branch and push.

            Opus 4.6

            1. I@IvanTheGeek
                2026-03-14 11:47:43.689Z

                check each branch of wasm-added, wasm-only, experiment, and main and if there are any files that need commited, do a commit for that branch and push to GitHub.

                Sonnet 4.6

                1. I@IvanTheGeek
                    2026-03-14 12:07:11.884Z

                    C:\CODE\EM-1\MyApp\publish\wasm\wwwroot

                    the wasm release publish did not produce an index.html
                    please fix
                    then commit in wasm-added branch and push

                    sonnet 4.6

                2. In reply toIvanTheGeek:
                  I@IvanTheGeek
                    2026-03-14 13:34:42.604Z

                    i ran "dotnet publish src\MyApp.Client\MyApp.Client.fsproj -c Release -p:HostingMode=WasmOnly -o publish\wasm" and uploaded the wwwroot to fastmail files which allows static hosting. The files were uploaded and accessed at https://em1.ivanthegeek.com/wwwroot/ using edge, I am still getting the "Loading..." and never the app. I am attaching the console and .har files to help investigate.
                    figure out the error, fix, verify, and then commit making sure the commit reaches the branch "wasm-added" and push and also make sure that when i run the dontnet publish in a windows cmd window that the files it is using is the "wasm-added" branch.

                    FILES: https://user.fm/files/v2-d182dde32fa2a5400fb510b514c4598f/files.zip