I’m creating a SPA in Purescript but there will be links that will point to a different SPA. I think in the micro-frontends jargon is called a Linked SPA composition. In order to keep the look and feel consistent between SPAs I want to extract common Halogen components (Navbar, footer, etc…) into a Purescript module.
But here is where I cannot find an example (maybe my fault) about how to develop a local Purescript module that won’t be published in Pursuit but that needs to be accessed by other apps.
Basically I want this structure:
.
├── common
├── main_spa
├── spa_1
└── spa_2
Where main_spa
, spa_X
have a build dependency through library versioning to common
.
How can I accomplish this?