Elm library to pair with my Go backend

mystique09 · November 25, 2022, 4:04pm

Hi, this is my first time asking here. I have a backend made with Go, now I want to pair it with Elm but I don’t know what will be the best fit library to use. I saw elm-spa and elm-pages, but I’m confuse what to pick, btw my frontend also needs authentication, and routing guard. TIA.

mattpiz · November 25, 2022, 5:19pm

Hi @mystique09. Basically all elm application use what is called TEA (The Elm Architecture). Using elm in the frontend is very much the same whatever backend you use. You simply need to be able to serve an html and a JS file (where the JS is the result from elm compilation). Some more info about that in the guide.

Regarding how your app is organized, many like the way Richard’s “Real World” example app is structured.
Now there also exists a few helper frameworks such as Elm Land (successor to elm-spa).
And a few static site generator libraries such as elm-pages.

If not already, I’d suggest registering to the elm slack, where you can more easily find out what really fits your needs.

cbrake · November 29, 2022, 7:58pm

I use elm-spa and like it a lot. Here is repo:

api and frontend directories may be of interest. We build and compress the elm.js file (only 50KB) and then embed that using go-embed. We then serve the compressed file by using this HTTP wrapper that decompresses the file on the fly:

github.com

simpleiot/simpleiot/blob/master/server/server.go#L329


      
          	}
          
          
	// remove output dir name from frontend assets filesystem
          	feFS, err := fs.Sub(frontend.Content, "public")
          	if err != nil {
          		log.Fatal("Error getting frontend subtree: ", err)
          	}
          
          
	// wrap with fs that will automatically look for and decompress gz
          	// versions of files.
          	feFSDecomp := newFsDecomp(feFS)
          
          
	// ====================================
          	// HTTP API
          	// ====================================
          	httpAPI := api.NewServer(api.ServerArgs{
          		Port:       o.HTTPPort,
          		NatsWSPort: o.NatsWSPort,
          		Filesystem: http.FS(feFSDecomp),
          		Debug:      o.DebugHTTP,
          		JwtAuth:    auth,

github.com

simpleiot/simpleiot/blob/master/server/fs-decomp.go

package server

import (
	"bytes"
	"compress/gzip"
	"io/fs"
	"strings"
	"time"
)

// fsDecomp can be used to wrap a fs.FS. If a file is requested and not found,
// we look for a .gz version. If the .gz version is found, we decompress it
// and return the contents. This allows us to ship .gz compressed embedded files
// but still serve uncompressed files.
type fsDecomp struct {
	fs fs.FS
}

func newFsDecomp(fs fs.FS) *fsDecomp {
	return &fsDecomp{fs: fs}

This file has been truncated. show original

system · December 9, 2022, 7:59pm

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.

Topic		Replies	Views
Backend apps with Elm: elm-express Show and Tell	8	2297	May 9, 2023
Fancy some GUI programming with Elm? Show and Tell	25	3771	June 3, 2022
Basic app architecture questions Learn	9	1145	April 10, 2020
Elm in Production Show and Tell	7	2011	December 12, 2018
UI Composition with Elm & Microservices Request Feedback	7	3240	May 14, 2018

Elm library to pair with my Go backend

Related topics