Description of Proposed Feature
As of create-single-spa@5, root configs expect all microfrontends to output to ESM, by default. I don't know how the single-spa-angular build works anymore - in the react ecosystem we have shared webpack configs and what I remember is that single-spa-angular had a shared webpack config, too. The outputSystemJS option might be a good naming convention for a configuration option within single-spa-angular for those who wish to continue using the latest versions of single-spa-angular without upgrading everything to esm first.
In what way would you use it?
The single-spa issue queues are people asking how to migrate Angular apps.
Description of Proposed Feature
As of create-single-spa@5, root configs expect all microfrontends to output to ESM, by default. I don't know how the single-spa-angular build works anymore - in the react ecosystem we have shared webpack configs and what I remember is that single-spa-angular had a shared webpack config, too. The
outputSystemJSoption might be a good naming convention for a configuration option within single-spa-angular for those who wish to continue using the latest versions of single-spa-angular without upgrading everything to esm first.In what way would you use it?
The single-spa issue queues are people asking how to migrate Angular apps.