dart-lang
evaluate whether it is worth switching from build-runner to frontend-server
As mentioned in https://github.com/dart-lang/sdk/issues/50664#issuecomment-1347089380 we may want to consider whether it makes sense for webdev to switch to use a front-end-server solution for all uses, and not just for flutter.
There are many open questions to consider:
- analyze the tradeoffs between the two
- how to support sourcegen?
- how to centralize frontend server and expose it from the Dart SDK
Related: https://github.com/dart-lang/webdev/issues/1591
If we switch to only using the FrontendServer (or even if we don't) I think it would make sense for the FrontendServer to be responsible for generating the necessary dill & JS files, instead of Flutter doing so.
Related to issue #1827
This could have many potential benefits, such as improved performance and scalability. However, there are also trade-offs to consider, such as the added complexity of implementing and maintaining a front-end-server, and how it would impact the development workflow.
It is also important to consider how to support sourcegen, as well as how to centralize the front-end server and make it accessible from the Dart SDK.
We should definitely look into this if it means we can remove the remaining uses of build_runner.
