You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Compile-time styling (StyleX) can't see styles declared in .rx: imports are aliased and top-level bindings live inside the module factory #81
Compile-time styling libraries can't see styles written in .rx. StyleX is the case we hit; vanilla-extract, Panda and similar tools have the same constraint.
What happens
import pure { attrs, create } from "@stylexjs/stylex"
local = create({ hint: { color: "red" } })
export component Hint() {
<p {...attrs(local.hint)}>hint</p>
}
rxc check passes. In the browser: Unexpected 'stylex.create' call at runtime. Styles must be compiled by '@stylexjs/babel-plugin', and Solid halts the reactive system (REACTIVITY_HALTED).
Why
Two things stack:
No plugin sees the lowered code in time.@stylexjs/unplugin is enforce: 'pre' and only transforms JS-like ids. .rx becomes JS inside @solidjs/vite-plugin's transform (the frontends hook), after every pre plugin has already passed over the raw .rx text.
Even if one did, the output isn't analyzable. Compile-time styling needs create({...}) at module top level, with literal arguments and the import binding used directly. The crate's output aliases every import (import { create as w$create } … const v$create = w$create) and moves every top-level declaration inside export default function module(__rt) { … }, where local is a __rt.memo.
Today's workaround (works)
Declare styles in a sibling .ts module and import the compiled object: import pure { s } from "./form.styles", then attrs(s.form, props.styles). Recipe functions from a StyleX design system (import pure { button } from "…/stylex/button") also work unchanged. We verified this end to end with SSR and hydration on Solid 2.0.0-rc.21, @solidjs/vite-plugin 3.0.0-next.57 and compiler/runtime 0.3.1.
Suggestion
A module-scope form that lowers verbatim. For example, a top-level binding whose right-hand side is a call to an imported pure function with literal arguments (or an explicit keyword) is emitted outside the module factory, and the import it calls stays unaliased. Styling compilers could then process .rx output the way they process .tsx.
Plugin ordering, in @solidjs/vite-plugin. Let other plugins see a frontend's lowered JS. For example, lower in load, or document a hook point a styling plugin can run after. This depends on the first point; on its own it doesn't help.
Is compile-time CSS-in-JS a goal for .rx? Or is the scoped <style> (spec/07 CSS-1…5) the intended answer, with a sibling .ts for StyleX? Either answer is useful; if the latter, a line in guide/libraries.md would save the next person the runtime crash.
Activity