reflex-dev
reflex
Blog
Docs
Changelog
Blog
Docs
Changelog
Overview
Branches
Benchmarks
Runs
Performance History
Latest Results
ENG-9809: Make sign in button reditect to login
carlos/update-sign-in-redirect
5 hours ago
preview: drop internal=True on REFLEX_NO_AUTOPREFIXER so the name matches what postcss.config.js reads
dev-build-mode
15 hours ago
Rename dev-build mode to preview Per review feedback, align the new run mode's name with the frontend-ecosystem convention (Vite/Next/Nuxt 'preview').
dev-build-mode
15 hours ago
dev-build: apply biome formatting to postcss.config.js template
dev-build-mode
15 hours ago
dev-build: address review feedback + add changelog - app.py: guard build.build() on hot reload so a failed frontend build keeps serving the previous build instead of taking the backend down. - postcss.config.js: make REFLEX_NO_AUTOPREFIXER honor falsy values ("false", "0", "") so the override actually works; keep the autoprefixer entry on a single line for the tailwind config rewriters. - Send a distinct "run-dev-build" telemetry event. - Add news fragments for reflex and reflex-base.
dev-build-mode
15 hours ago
Add dev-build run mode `reflex run --env dev-build` hot reloads like `dev`, but instead of running the Vite dev server it serves a freshly built (un-minified) frontend bundle mounted into the backend on a single port. Each backend hot reload re-runs the frontend build against the newly compiled output; a manual browser refresh shows changes. This trades the always-on Vite dev server's overhead for cold rebuilds while staying close to dev semantics. To keep rebuilds fast and output debuggable, dev-build disables (overridable): - JS + CSS minification (VITE_MINIFY -> build.minify / build.cssMinify) - autoprefixer (REFLEX_NO_AUTOPREFIXER, read by the generated postcss.config.js) - sourcemaps stay off (the default) Also threads VITE_MINIFY into the vite config, restricts `export --env` to dev/prod, and fixes `run`'s env parsing to honor the new value.
dev-build-mode
16 hours ago
fix: don't treat reflex_components_* as framework packages The reflex_components_* prefix is the convention community component libraries follow, so prefix-matching it as framework wrongly steered those modules' memos away from their real package name. Match framework packages by exact name or dot boundary only.
FarhanAliRaza:memoize-file-path-mirror
18 hours ago
fix: disambiguate same-named memos across modules by per-module symbol Two memos sharing a name in different modules mirrored to distinct files but still exported and imported the same JS identifier, so a page using both hit a tag collision. Derive a per-module-unique symbol (name plus a short hash of the dotted module) via the new memo_paths.library_and_symbol, and route every compiled tag/import/name through it. Key the MEMOS registry by (name, source_module) so same-named memos in different modules coexist rather than overwriting each other, while a genuine same-module shadow still resolves last-wins.
FarhanAliRaza:memoize-file-path-mirror
22 hours ago
Latest Branches
CodSpeed Performance Gauge
0%
ENG-9809: Make sign in button reditect to login
#6664
5 hours ago
8e50c22
carlos/update-sign-in-redirect
CodSpeed Performance Gauge
0%
Add preview run mode
#6663
15 hours ago
ff68e20
dev-build-mode
CodSpeed Performance Gauge
0%
feat(compiler): mirror memo output paths to Python source modules
#6457
18 hours ago
78660dd
FarhanAliRaza:memoize-file-path-mirror
© 2026 CodSpeed Technology
Home
Terms
Privacy
Docs