elm-pages-3-alpha-starter

This is a starter to try the elm-pages 3.0 alpha. github

Question for Dillion slack , at blog.dreyeck.ch I am experimenting with your elm-pages-3-alpha-starter. I have replaced the blog with a view route commit Now inspecting the page I see “elm-pages is up and running!” The message is: Hello! but then “This page could not be found.” (which you will see immediately without using the Debugger, Inspect) Do I need the said Elm-Pages Adapter or would it be more clever in my case to remove all netlify related parts of your code (redirects etc)? Would there be a starter for my Federated Wiki running on a NixOS server scenario? […]

By the way, I had to modify the generated index.html : replace the absolute path with the relative path to the .js and .css files. How could I adjust the build process accordingly?

blaix 1:52 PM via slack @dillonkearns were you picturing the adapter generating that server.js file? And if we wanted to share something like this would you like a PR to elm pages or people publishing standalone packages?

dillonkearns 6:41 PM This is very cool @blaix , so glad you're finding it easy enough to build something now! It was tricky to wrangle it to find the simpler thing, but now that I've got it it feels really natural to just give a file with that simple render function interface. I started a GitHub Discussion thread about adapters. I think it would be great to discuss questions, implementations, and ideas over there as I'm sure people will want to explore a lot of different frameworks/hosts. page . I would love it if people would chime in over there and share their ideas or what they've been able to build!

It looks like the SvelteKit Node adapter generates both (a file with a handler function, which I assume is a connect compliant middleware, as well as a full file that runs a server with that all wired in): page