Replies: 2 comments
-
|
Duplicate of ethanblake4/dart_eval#24 |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Moved this to a discussion, but it's actually not a duplicate. ethanblake4/dart_eval#24 is about tree-shaking for code inside dart_eval, not about how it prevents the Dart compiler from tree-shaking code outside dart_eval. TBH, I don't know how it would be possible to fix that, but I'll leave this open for any ideas. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
In order to support all flutter api, we seem to need to finally bridge all of them. Then, Flutter tree shaking is effectively disabled, causing the size to be larger.
This may not be a problem for complicated apps (apps which needs hot update I guess are mainly also large), since they already use a large portion of the framework. Anyway just write down my thoughts about this potential problem.
Beta Was this translation helpful? Give feedback.
All reactions