Skip to content
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

Update separating-applications.md #329

Merged
merged 3 commits into from
Sep 26, 2020
Merged

Update separating-applications.md #329

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
c38d055
Update separating-applications.md
kristianmandrup Sep 21, 2020
7a2968d
Update website/versioned_docs/version-5.x/separating-applications.md
joeldenning Sep 26, 2020
f239681
Update website/versioned_docs/version-5.x/separating-applications.md
joeldenning Sep 26, 2020
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
12 changes: 8 additions & 4 deletions website/versioned_docs/version-5.x/separating-applications.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,8 +30,6 @@ Create a root application that npm installs each of the single-spa applications.

Typically, the single-spa applications compile themselves separately with babel and/or webpack.

Note that you can also use the [monorepo methodology](https://medium.com/netscape/the-case-for-monorepos-907c1361708a) which allows for separate builds without having separate code repositories.

Advantages:

- npm install is familiar and easy to set up
Expand All @@ -42,7 +40,13 @@ Disadvantages:
- The root application must reinstall the child applications in order to rebuild/redeploy
- Medium difficulty to set up

#### Option 3: Dynamic Module Loading
#### Option 3: Monorepos

Create a [monorepo](https://medium.com/netscape/the-case-for-monorepos-907c1361708a) with multiple SPAs in a single (mono) repo.
This allows for separate builds and deployment without having separate code repositories.


#### Option 4: Dynamic Module Loading

Create a root application which can allow single-spa applications to deploy themselves separately. To do so,
create a manifest file that the single-spa applications update during their deployment process, which controls
Expand All @@ -57,6 +61,6 @@ Changing which JavaScript file is loaded for each child application can be done

| | Separate code repositories possible | Independent CI builds | Separate deployments | Examples |
| - | ----------------------------------- | --------------- | -------------------- | -------- |
| Monorepo | :x: | :x: | :x: | — |
| NPM Packages | :white_check_mark: | :white_check_mark: | :x: | [1](https://github.com/jualoppaz/single-spa-login-example-with-npm-packages) |
| Monorepo | :x: | :white_check_mark: [1](https://medium.com/labs42/monorepo-with-circleci-conditional-workflows-69e65d3f1bd0) | :white_check_mark: [1](https://medium.com/labs42/monorepo-with-circleci-conditional-workflows-69e65d3f1bd0) | — |
| Module loading | :white_check_mark: | :white_check_mark: | :white_check_mark: | [1](https://github.com/react-microfrontends/) [2](https://github.com/vue-microfrontends/) [3](https://github.com/polyglot-microfrontends/) |