-
-
Notifications
You must be signed in to change notification settings - Fork 78
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.
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
Multiple Assets on Angular 11, single-spa >=4.0.0 and single-spa-angular ^4.9.2 #373
Comments
Are you referring to javascript source maps not working in the browser devtools?
Those warnings are expected and do not cause issues. |
Yes, I don't see the ts files. Without ts files the debuging is very complex |
I don't spend much time supporting single-spa-angular, but if you have time to investigate this and submit a PR, I am happy to review it. There are also a few others who help maintain the project who may be able to help. Source maps are controlled via webpack's |
Hi, I think the problem comes from the |
I noticed duplicated sourcemaps in my build (two I checked the difference between the original Webpack config and the one after Idk why single-spa-angular decided to enable it, since Angular uses
Finally, I set I'm using:
|
Hi,
I started an application with angular 11 and I included single-spa-angular.
When I launch
ng build --watch
command, i receive these warningsWarning: ...\__ivy_ngcc__\fesm2015\single-spa-angular.js depends on 'single-spa-angular/internals'. CommonJS or AMD dependencies can cause optimization bailouts. For more info see: https://angular.io/guide/build#configuring-commonjs-dependencies
Warning: Conflict: Multiple assets emit different content to the same filename main.js.map
The problem is that i don't see the ts files on console for debug the app.
An example on this repo:
https://github.com/giolongo/single-spa-angular-11.git
For generating this application I lunched these commands:
ng new my-app --routing --prefix my-app
cd my-app
ng add single-spa-angular
The text was updated successfully, but these errors were encountered: