Loading angular apps (different versions) inside root appliatin with singleSpaEntry exposed inside each app about single-spa-portal-example HOT 7 OPEN

The Angular CLI does not compile the App as UMD module. And therefore system.js in the portal app can't load it.

You need a custom webpack.config.js which defines all the necessary steps to compile the Angular app with singleSpaEntry.js as entry file to a UMD module.

Take a look in the folder "app5Angular" which is an Angular 6 app that works.

from single-spa-portal-example.

So, if we have a team working with a project generate with angular-cli, we need to eject the build to do with webpack? it's posible to mantain both configurations (angular-cli and webpack.config) in the same project?

from single-spa-portal-example.

Also, I am getting the same issue...
Uncaught Error: Application 'app6' died in status LOADING_SOURCE_CODE: Unable to dynamically transpile ES module A loader plugin needs to be configured via SystemJS.config({ transpiler: 'transpiler-module' }). Instantiating http://localhost:9000/app6/singleSpaEntry.js Loading /app6/singleSpaEntry.js

Is there any way to load angular 6 cli app with singleSpaEntry.js?
appreciate your help...

from single-spa-portal-example.

Did you find a way around this? I am also having this issue.

from single-spa-portal-example.

@fireappsAdmin @kgamalseif
This question has already an answer, you need to eject your apps (if possible) and then create a custom webpack.config -> Take a look in the folder "app5Angular" which is an Angular 6 app that works. Or have a look below.

@adrianlemess
I created an Angular 6 app (which doesn't have the ng eject option anymore and used "@angular-builders/custom-webpack": "^2.5.4", then in my angular.json you have to update the build options like this:
"build": { "builder": "@angular-devkit/build-angular:browser",

You'll find more info at the package website. Anyways if you place just the webpack.config.js in your root folder and add the npm run watch:portal from the example Angular apps it'll work and serve the app to the portal.

from single-spa-portal-example.

@maciej-w
Thanks for reply, I also used the app5Angular as a guide, and unfortunately got the same error.

I am able to browse my app after npm run watch:portal as below, but got the LOADING_SOURCE_CODE error when browsing using portal.

Appreciate your help...

from single-spa-portal-example.

@kgamalseif - I can see that this is a different app than form the example. To me it looks like your module is not building correctly, without looking at the code I'm not able to help. Please follow this to check if your code follows best practices: Angular AOT

from single-spa-portal-example.