Skip to content

Document how the build output is chosen #8

@asheshambasta

Description

@asheshambasta

As I play with this further, another thing is very confusing: when do we use JSaddle-warp and when not?
Here's what I did:

  • Took the reflex-stone as my template, and created a multi-project cabal.project based project. The project had the following directories:
  • frontend
  • backend
  • data
  • api

(since I was planning to use Servant and Servant reflex).

The frontend.cabal file remained mostly unchanged from the initial state.
The perplexing thing is (and I cannot see any reason why this is happening), is that in the original (stone) project, running main calls mainWidget ...; which seems to fire up a warp server when called from the REPL (GHCI).
In my project, when I try to do the same, for some reason, I'm greeted with a GUI (with some sort of DOM based UI).

There are some extra dependencies in the derived project, but everything else seems identical. And I've so far been unable to find out why.

A good discussion on JSaddle warp etc. may help with this kind of confusion.


I'm now looking into JSaddle warp on how to call run explicitly that fires up a warp server instead of the GUI.
I've also opened reflex-frp/reflex-platform#696 since I feel this must be documented on reflex-platform too.

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentation

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions