Latest Results
fix(init): declare RadixThemesPlugin in default rxconfig template (#6776)
* fix(init): declare RadixThemesPlugin in default rxconfig template
The blank app template renders Radix Themes components (rx.heading, rx.text,
rx.code, rx.button), which auto-enable the Radix plugin at compile time. The
generated rxconfig.py did not list RadixThemesPlugin, so the compiler fell back
to implicit enablement and emitted the "Implicit Radix Themes enablement has
been deprecated in version 0.9.0" warning on the first `reflex run` of every
freshly scaffolded app.
Declare rx.plugins.RadixThemesPlugin() explicitly in the config template (kept
last to preserve the existing plugin/stylesheet ordering the implicit path
used), which is the exact remedy the deprecation message instructs users to
apply. New apps are now warning-free.
closes #6483
* fix(radix): keep deprecated App(theme=...) applied with an explicit RadixThemesPlugin
Declaring RadixThemesPlugin() in the default rxconfig template routed
App(theme=...) into apply_app_theme's explicit-plugin early return, which
silently dropped the theme in freshly scaffolded apps (the pattern all
theming docs teach). Remove the guard so the deprecated parameter keeps
working, and winning, until its 1.0 removal, matching pre-plugin behavior.
Also add news fragments for the changelog check.
---------
Co-authored-by: Farhan Ali Raza <62690310+FarhanAliRaza@users.noreply.github.com>
Co-authored-by: Farhan <www.mfarvirus@gmail.com> Enable the development condition for react-router dev under bun
react-router 8's dev CLI imports "#development-condition-enabled", a
resolution probe that is true only when the runtime has the
`development` export condition active. When it is not, the CLI
re-executes itself with NODE_OPTIONS=--conditions=development; bun does
not apply that option when it executes the CLI on installs without
node, so the restarted process probes false again and trips the CLI's
restart guard: "restartWithMergedOptions() was called, but the process
has already been restarted", killing the dev server. This is the second
react-router 8.3.0 fallout in reflex-init-in-docker-test - the run on
this branch got past the (fixed) prerender failure, crashed here in the
dev phase, and hung the workflow waiting on a frontend that had exited.
Environments with node installed never see it because the CLI's node
shebang wins, which is why the integration matrix stayed green.
Pre-enable the condition in run_frontend for both runtimes by appending
--conditions=development to NODE_OPTIONS and BUN_OPTIONS (merged with
any existing value, idempotent). Under bun the CLI's restarted process
picks BUN_OPTIONS up from the environment and comes up with the
condition enabled; under node the condition is active up front and the
restart is skipped entirely. Prod is unaffected: run_frontend_prod
serves compiled static files without the react-router CLI, and vite's
bundle resolution conditions are mode-driven, not process-driven.
Verified in a node-free environment (reflex-managed bun 1.3.14,
mirroring the docker image): `reflex run --env dev` on a fresh blank
app now serves 200 with zero restart errors, where it previously
reproduced the CI crash exactly.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01AzeRM83L6J367wmwk9Gezkclaude/vite-8-2-0-test-memo-regression-h6shlg Latest Branches
0%
issue-6484-code-block-tests 0%
claude/vite-8-2-0-test-memo-regression-h6shlg 0%
agent/keyword-only-algolia-search © 2026 CodSpeed Technology