Adding vike support for Purescript Deku

[mikesol]

Hi! I'm the lead developer of PureScript Deku. I'm reading https://vike.dev/ui-framework and it recommends opening up an issue here to kick off the process of a vike integration. Thanks in advance for any resources or pointers!

[brillout]

Hi Mike, sounds interesting! What I recommend is to have a look at the minimal integrations /examples/react-minimal and /examples/vue-minimal (see root of this repo) and see if you can get a rough Vike + Deku example going. That alone would be lovely and we could create a vike.dev/deku page and link to that example.

Then, we can flesh out the example to something more full-fledged, see for example boilerplates/boilerplate-* (or $ pnpm create vike).

Once we have a satisfactory example going, we can create a Vike extension vike-deku or a framework that completely wraps Vike.

I guess the biggest question here is how to interop Vike with PureScript. Not sure if it's easily feasible with a friendly DX?

Feel free to let me know if you run into blockers.

[brillout]

I just had a look at https://github.com/mikesol/vike-deku-client-routing and it seems like you don't want to use Filesystem Routing? Because it isn't functional enough for your taste? I'm seeing src/Vike/ClientRouting/Pages/Route.purs and I wonder what concrete disadvantage you see in Filesystem Routing.

[mikesol]

Hi!
I'm definitely open to using filesystem routing.
The issue I ran into with it is that it created boilerplate, as the JS files only wound up importing Purescript logic. They could be auto-generated from the Purescript naming conventions at build time, but that seemed like a heavier lift than Route.purs.

[brillout]

👍 Feel free to let me know if you need something on Vike's side, although note that we have quite a cramped roadmap already.

[mikesol]

All's good! If you think the repo is up to standards, it'd be nice to make an integration. I can of course use file system routing if you prefer 👍

[brillout]

I guess the best would be to create vike-deku under your GitHub name so that you're then free to go in whichever direction you feel like :) I'll happily list it in Vike's docs.