You can get pretty far with progressive-web-apps, but you’ll have some “wiring” written in javascript. Also, if you have major features that rely on stuff Elm can’t do on it’s own, it might get hairy if you don’t like JavaScript/TypeScript.
My approach has been:
- build the Elm-project, where only the little bit of JavaScript required to initialize the app and setup ports is written
- Build typescript-modules for specific features, ensure they have nice autocomplete in VS-Code, and deploy them to NPM for import into the main project.
The core team is being really ambitious about what Elms APIs should look like, and for that reason, they’re taking their sweet time getting support for a lot of stuff. Ports are nice once you get the hang of it 