ReferenceProjects/example-spa-elm-app
1
0
Fork 0
Code Issues 1 Pull requests Actions Packages Projects Releases Wiki Activity
Example demonstrating how one might architect a single page application Elm app with Rust as the backend.
19 commits 1 branch 0 tags 226 KiB
Elm 54.2%
Rust 27.8%
Nix 7.9%
JavaScript 4.5%
Makefile 3%
Other 2.6%
Find a file
Artturin 9ebdbdb36a Makefile: fix frontend build 
Its make was moved to `serve` target in ccec612687, but we can't use `serve` target in the nix build

It's also run after `frontend` target is already built which probably causes the `frontend` target to build.
2025-01-04 01:08:26 +02:00
backend now using mod landing as its own module 2025-01-02 23:24:10 -05:00
frontend Add flake 2025-01-04 00:56:19 +02:00
.gitignore Add flake 2025-01-04 00:56:19 +02:00
default.nix Add flake 2025-01-04 00:56:19 +02:00
flake.lock Add flake 2025-01-04 00:56:19 +02:00
flake.nix Add flake 2025-01-04 00:56:19 +02:00
Makefile Makefile: fix frontend build 2025-01-04 01:08:26 +02:00
README.md drastically improve build scripts 2025-01-03 13:29:56 +00:00
shell.nix Add flake 2025-01-04 00:56:19 +02:00

README.md

About

Example demonstrating how one might architect a single page application Elm app.

Building

nix-shell -p elmPackages.elm cargo uglify-js
make serve RELEASE=1 # can also do DEBUG=1 instead

Now open http://127.0.0.1:8080 in your browser.

TODO

  • Add Makefile
  • EventHandlers.onMessage should inject successfully decoded message into Msg type directly...
  • Run uglify twice as per this link
  • JSONify backend code for all send/receive
  • Backend should only communicate over websocket
  • Close websocket after 15s of no response(from frontend) to websocket pings
  • Implement dark mode
  • Add GPLV3 License
  • Add make release target that is nix ready...
  • Add default.nix