Activity

1. alan-agius4 commented on Apr 2, 2021

   

   alan-agius4

   on Apr 2, 2021

   Collaborator

   More actions

   Hi @glebmachine,

   Thanks for opening this issue. While the Angular CLI allows extending the Webpack configuration by doing so you are venturing on the unsupported path as Angular tooling team doesn't provide support for builds using custom Webpack configurations.

   I suggest that you file an issue https://github.com/angular-architects/module-federation-plugin and raise an issue with the author of this package. If is indeed an Angular CLI issue which cannot be solved by the above mentioned 3rd party package please feel
2. alan-agius4

   closed this as completedon Apr 2, 2021
3. glebmachine commented on Apr 4, 2021

   

   glebmachine

   on Apr 4, 2021

   Last edited by glebmachine

   Author

   More actions

   @alan-agius4 Unfortunately, this is not

   I found that if build phase stuck with .ts extenion at the and of an shared dependency import path
   (also i checked vanilla webpack + module federation build - everything works fine, proof)

   I think it's one of the angular-cli devkit extensions, that breaks compilation process silently

   Here updated by example, with ultra clean repro (inly cli and Module Federation)
   https://github.com/glebmachine/module-federation-build-stuck

   Steps to reproduce:

   1. git clone git@github.com:glebmachine/module-federation-build-stuck.git
   2. yarn
   3. ./node_modules/.bin/ng run shell:serve
   4. It hangs
   5. Remove unnecessary .ts extension (screenshot below) and run again (wuola! Building phase completes)
      
4. glebmachine commented on Apr 4, 2021

   

   glebmachine

   on Apr 4, 2021

   Author

   More actions

   @alan-agius4 please, reopen
5. alan-agius4 commented on Apr 4, 2021

   

   alan-agius4

   on Apr 4, 2021

   Collaborator

   More actions

   Hi, @glebmachine,

   Following some further discussion with @clydin.

   Webpack 5 is still experimental in v11 and even without that, modifying the internal Webpack configuration in complex ways is not guaranteed to work nor supported.

   If you’d like to troubleshoot and come up with a fix, we can evaluate it, but Webpack 5 should be expected to not be fully functional in v11.
6. glebmachine commented on Apr 4, 2021

   

   glebmachine

   on Apr 4, 2021

   Last edited by glebmachine

   Author

   More actions

   Yeah, i'm not expecting that, but in 12 preview build it emits zero sized bundle and don't serve anything
   (you can find more information here #20428)

   I'm just trying to find the way to run module federation, and brings you some bugs. as early adopter
   I hope you implement module federation support because angular is about big enterprise applications, which need to be splitted into microfrontends.

   About "modifying the internal Webpack configuration"
   It's just built-in webpack plugin (module federation). It's not some huge modification. Just single canonical webpack config.

   Microfrontends is very important thing in 2021 and module federation - key feature for implementing them, don't dismiss that, maybe @clydin have some thoughts about that, or reasons not to support module federation in angular ecosystem?

   Related to feature request: #17556

   👍React with 👍2Reacted by Łukasz Rekucki and Hardik Patel
7. angular-automatic-lock-bot commented on May 5, 2021

   

   angular-automatic-lock-botBot

   on May 5, 2021

   More actions

   This issue has been automatically locked due to inactivity.
   Please file a new issue if you are encountering a similar or related problem.

   Read more about our automatic conversation locking policy.

   _{This action has been performed automatically by a bot.}
8. angular-automatic-lock-bot

   locked and limited conversation to collaborators on May 5, 2021