Describe the Enhancement you want
I want a compilation mode for reflex that generates the output javascript app and updates package.json and bun.lock without actually installing the frontend packages. This would allow me to subsequently run bun install --frozen-lockfile and bun run dev to start the development server without having to run through reflex. It would also be cool if the output was made pretty and stable when using this interface so the generated code and artifacts could be checked in and tracked for changes.
- Which feature do you want to improve? (and what problem does it have)
reflex compile installs packages for "no reason" since it doesn't actually run the app.
- What is the benefit of the enhancement?
It would make more semantic sense if reflex commands had the following structure:
reflex init - creates a new app / refreshes the common templated frontend filesreflex compile - performs init, if needed. generates frontend javascript app and package.json / bun.lockreflex run - performs compile, if needed. installs frontend packages and starts frontend+backendreflex export - performs compile, if needed. produces static frontend export for running in prod mode or externally
In some deploy or testing use cases, it's helpful to break up these steps. Particularly it would be nice to not have to recompile to export or run when recompiling is not needed.
Describe the Enhancement you want
I want a compilation mode for reflex that generates the output javascript app and updates package.json and bun.lock without actually installing the frontend packages. This would allow me to subsequently run
bun install --frozen-lockfileandbun run devto start the development server without having to run through reflex. It would also be cool if the output was made pretty and stable when using this interface so the generated code and artifacts could be checked in and tracked for changes.reflex compileinstalls packages for "no reason" since it doesn't actually run the app.It would make more semantic sense if reflex commands had the following structure:
reflex init- creates a new app / refreshes the common templated frontend filesreflex compile- performs init, if needed. generates frontend javascript app and package.json / bun.lockreflex run- performs compile, if needed. installs frontend packages and starts frontend+backendreflex export- performs compile, if needed. produces static frontend export for running in prod mode or externallyIn some deploy or testing use cases, it's helpful to break up these steps. Particularly it would be nice to not have to recompile to export or run when recompiling is not needed.