Duplicate Check
Describe the requested feature
Most extensions, like "flet-dropzone", require the project to be compiled with "flet build", so that the dart extensions get included into the frontend assets.
But for the web platforms, it means everything must be compiled, even the python code (with pyodide), which is not always possible eg. due to pydantic and its rust extensions.
It's possible to manually build only the flutter project, change "pyodide:" attribute to false in the index.html, and then use the "FLET_WEB_PATH=xxx/build/flutter/build/web" env var so that "flet run --web" delivers the proper, augmented, flutter widget pack, but it's quite complex.
Suggest a solution
How about adding some flags so that it's possible to build only the flutter/dart part of the web runtime, and keep python execution on the server-side ? And "flet run --web" should be able to detect and load it in preference to the builtin flutter widget pack.
Screenshots
No response
Additional details
No response
Duplicate Check
Describe the requested feature
Most extensions, like "flet-dropzone", require the project to be compiled with "flet build", so that the dart extensions get included into the frontend assets.
But for the web platforms, it means everything must be compiled, even the python code (with pyodide), which is not always possible eg. due to pydantic and its rust extensions.
It's possible to manually build only the flutter project, change "pyodide:" attribute to false in the index.html, and then use the "FLET_WEB_PATH=xxx/build/flutter/build/web" env var so that "flet run --web" delivers the proper, augmented, flutter widget pack, but it's quite complex.
Suggest a solution
How about adding some flags so that it's possible to build only the flutter/dart part of the web runtime, and keep python execution on the server-side ? And "flet run --web" should be able to detect and load it in preference to the builtin flutter widget pack.
Screenshots
No response
Additional details
No response