Skip to content

monorepo multiple main modules documentation #1339

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

monorepo multiple main modules documentation #1339

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
25 changes: 25 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -831,6 +831,31 @@ The `--package` flag is also available for many more commands, such as `build`,

An important property of this "monorepo setup" is that the `output` folder will be shared between all the packages: they will share the same build package set (or build plan when using the solver) and they will be all build together.

#### Multiple Main Modules

Given
```
.
├── app1
│ ├── spago.yaml
│ └── src
│ └── Main.purs
├── app2
│ ├── spago.yaml
│ └── src
│ └── Main.purs
└── spago.yaml
```

, to avoid the error `Module Main has been defined multiple times`:
* `app1` `Main.purs` can have `module Main1`
* `app2` `Main.purs` can have `module Main2`

From the root, run:
* `spago run -p app1 --main Main1`
or
* `spago run -p app2 --main Main2`

### Polyrepo support

There might be cases where you want to have multiple loosely-connected codebases in the same repository that do _not_ necessarily build together all the time. This is sometimes called [a "polyrepo"][monorepo-tools].
Expand Down
Loading