Skip to content

Latest commit

 

History

History
61 lines (53 loc) · 2 KB

README.md

File metadata and controls

61 lines (53 loc) · 2 KB
Raw

SingleSPA integrated into Angular

This is an example of SingleSPA working inside a Angular Application. The Angular Application takes the role of the Root App in this case.

PLEASE NOTE THAT THIS IS NOT A RECOMMENDED SETUP As explained in the FAQs of SingleSPA this approach will lead to a lot of Problems in the long run. But I discovered that such approaches could help people with existing scaled Angular Applications to deliver features to a "legacy" System while migrating to Single-SPA without the need to build features two times.

What does this contain

  1. An Angular Application which is configured to support the mounting of SingleSPA Components.
  2. One example Vue3 based Microfrontend to show how you can pass props from the Angular Application to a Microfrontend (Sorry for the different PackageManager (yarn/npm) was to lazy to fix it for such a small example).

How to get started

To see what you would need to change in your Angular Application take a look at this files:

package.json
src/index.html
src/assets/importmap.json
src/app/app.component.html
src/app/app.component.ts

Install by:

npm ci
cd examplemfe2
yarn

Start with:

npm run start

and

cd examplemfe2
yarn run serve

Specifics of Angular Versions

This list can contain Issues specific Angular Versions have. This of course is based on experience and is not complete.

Angular9 and SystemJs

Angular9 seems to have a global Variable System which is not our Browsers SystemJS. This leads to compile Errors:

ERROR in ./src/app/app.component.ts
Module not found: Error: Can't resolve '@single-spa/welcome' in '/src/app'

Not sure what this originates from but here is a way to work around it: Rename System in the index.html

<script>
  var SystemJS = System
</script>

And then use SystemJs instead of system for your calls app.components.ts:

declare var SystemJS: any;
...
SystemJs.import("you@your-mfe")