Working with SolidJS?

Solid signals or SolidStart SSR acting up? We unstick it.

SolidJS looks like React in the editor and behaves nothing like it under the hood, which trips up teams who ported a codebase in a weekend and then watched components stop updating for no visible reason. We read the reactive graph, find where a signal was destructured or a store was mutated the wrong way, and leave the app updating on exactly the inputs it should.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

solid-dev.log

still broken

What it is

SolidJS at a glance

SolidJS is a fine-grained reactive UI library created by Ryan Carniato and first released in 2018, with a 1.0 landing in 2021. It borrows JSX and component syntax from React, then throws out the virtual DOM and compiles components down to direct DOM updates driven by signals.

SolidStart is the official meta-framework, built on top of Vite and the h3 server, and handles routing, server functions, SSR and streaming. The combination appeals to teams who want React-shaped code with meaningfully smaller bundles and genuinely faster updates, and who are willing to learn a reactivity model that is strict about where values can be read.

Type
Reactive UI library with fine-grained updates
First released
2018
License
MIT
Maintained by
Ryan Carniato and the Solid core team
Typically used for
Performance-sensitive dashboards, interactive sites, Svelte or React alternatives where bundle size matters

The honest version

SolidJS pros and cons

No technology is all upside. This is where SolidJS earns its place and where it tends to cause trouble.

Where SolidJS is strong

  • Tiny bundles and fast updatesCompiled output goes straight to the DOM without a virtual tree in between, so bundles are a fraction of React's size and updates touch only the nodes that actually changed.
  • Signals as the primitivecreateSignal, createMemo and createEffect compose into pure, predictable graphs. There is no stale closure trap once the tracking rules click.
  • JSX and component syntax carry over from ReactAn engineer coming from React is productive on the second day. The muscle memory for component files, prop passing and conditional rendering mostly transfers.
  • Resources and Suspense for datacreateResource integrates with Suspense boundaries so loading states live in the right place in the tree, which keeps data code out of effect handlers.
  • SolidStart covers routing and SSRFile-based routes, server functions, streaming SSR and middleware are shipped as one package, so a new app does not start with half a dozen glue libraries.
  • Honest about what breaks and what does notError messages name specific reactivity rules and point at the file that broke them, which is more useful than a generic React warning.

Where SolidJS bites

  • Reactivity rules biteDestructuring props breaks reactivity, so does reading a signal outside a tracking scope. Developers coming from React spend their first week relearning habits they did not know they had.
  • Small ecosystemEvery category has fewer libraries than React or Vue. For niche needs the answer is often to port a library yourself or wrap a framework-agnostic one by hand.
  • Hiring is harderDevelopers with real production Solid experience are rare. A new hire who knows React will need onboarding time, which is a trade a lot of teams underestimate.
  • SolidStart is younger than it looksThe meta-framework has rough edges around deployment adapters, cache invalidation and error boundary behavior that are being worked on but will surface during a build.
  • Error traces are compiler outputStack traces point into compiled JSX, not the file you wrote. Source maps help, but debugging a reactivity bug still involves reading the generated graph.
  • Store API is its own learning curvecreateStore, produce() and reconcile have semantics you have to internalize before updates stop surprising you. The docs are good, but the shape of the API is not Redux and not useState.

Sound familiar?

Common SolidJS problems we fix

The SolidJS problems that bring people to us, and what you have once each one is fixed.

Making a reactive object into a non-reactive one by destructuring props

Components stop updating for no visible reason

A props object was destructured at the top of a function, which freezes the values at the moment of render. Everything looks right until a signal changes and nothing re-runs.

Reactivity preserved across the tree

Hydration Mismatch. Unable to find DOM nodes for hydration key

SolidStart hydration fails on first paint

Markup rendered on the server does not match what the client expects, usually because of a conditional that reads something server-only, or a For loop without a stable key.

Hydration completes cleanly

createSignal must be called inside a tracking scope

Signals leak outside a reactive owner

A createSignal call fired at module scope, or inside a handler that runs after disposal, leaving an orphaned computation and a warning in the console.

Signals owned by the right root

window is not defined

SSR crashes on a browser API

A component that reads window, document or localStorage during render runs on the server and throws before the first byte goes out.

Browser-only code gated to the client

Store update outside produce() mutated a frozen object

Store writes bounce off a frozen object

Direct mutation on a nested store property that was already handed back as a read-only slice. The update is silently dropped and the UI stays stale.

Store updates go through the right helper

TypeError: setStore is not a function

Context destructuring loses the setter

A context value destructured outside a reactive scope, which turned the setter into undefined by the time a child component tried to use it.

Context read inside the right scope

no server entry found at src/entry-server.tsx

SolidStart build fails on deploy

An adapter mismatch between the Vite config and the hosting target, a missing entry file after a template update, or a renamed import that was not followed through.

Entry points wired to the adapter

React port left half the components non-reactive

A ported-from-React app does not update

Hooks replaced one-for-one with signals, destructured props left in place, useState swapped for createSignal in the wrong scope. Everything compiles, nothing re-renders.

Full reactive pass through the codebase

What we do

SolidJS help, from rescue to steady state

Reach out for one stuck component, or hand us the Solid codebase and we take it from there.

Rescue
Updates that never fire, SSR that throws on first request, a SolidStart build that will not deploy. We get it responding first, then explain what the compiler was telling you.
React to Solid ports
A rewrite that keeps the UI and swaps the engine, with reactivity rules followed, destructuring untangled, and tests that prove the port behaves like the original.
SolidStart production readiness
Server functions, streaming SSR, cache semantics and the deploy adapter picked for the host you actually use, with the trade-offs made explicit.
Performance tuning
Signal graphs audited, memos placed where they earn their cost, and bundle analysis that shows the parts of the app worth splitting out.
Architecture review
Store design, context boundaries and route layout reviewed before a small decision becomes a hard one to unwind.
Managed Tech
Version bumps, Solid and SolidStart upgrade work, and a pair of eyes on the reactivity patterns as the team grows, so new features do not accidentally break the graph.

How it works

From first message to fixed

  1. Look Free estimate

    Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.

  2. Fix

    We fix the cause, not the symptom. If something is down, getting it back up comes first.

  3. Harden

    Backups, monitoring, updates and access, so the same problem can't quietly come back.

  4. Hand back or stay on

    You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.

Often found together

Running SolidJS alongside something else?

We work on the whole stack, so the problem can be wherever it actually is.

Questions

SolidJS questions

Something else? Call+1 737 727 7327

Why do our SolidJS components stop updating after a refactor?

Nine times out of ten the culprit is props destructuring. Writing const { name } = props at the top of a function freezes the value right there, and future signal changes never reach the component. The fix is to read props.name at the point of use, or to spread props into a merged object through the mergeProps helper so reactivity survives.

Can we port a React app to SolidJS without rewriting everything?

The components and JSX usually come across with small changes, but the state code almost always needs attention. useState maps onto createSignal, useEffect onto createEffect, and useMemo onto createMemo, yet the rules about where those can be called and read are stricter in Solid. We do the port in stages, run both apps side by side where possible, and prove the new one behaves before switching traffic.

Why does SolidStart show a hydration mismatch?

Hydration expects the server HTML and the client-rendered tree to line up exactly. A For loop without a stable key, a date formatted on the server in a different locale than the browser, or a component that reads window during render will all throw the mismatch. We work from the key in the warning back to the file that produced the differing output.

Is SolidJS a safe choice for a production app?

For a team that will own it and keep it current, yes. The core library is stable, the reactivity model is sound, and the performance gains over React are real on data-heavy screens. The cautions are ecosystem size and hiring, which matter more on a long-lived product with heavy turnover than on a focused team that writes its own primitives.

How do we handle data fetching in SolidJS?

createResource is the primary tool, and it integrates with Suspense so loading states live in the tree rather than in a pile of state flags. For mutations, SolidStart server functions give you a typed server round trip without a separate API layer. We set up the invalidation and error handling so a failed fetch does not freeze the UI.

How much does SolidJS help cost?

Quotes are free of charge. Share what the Solid app is meant to do and what is not happening, and we come back with pricing before writing any code.

Free estimate

SolidJS project giving you trouble?

Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.

  • No charge to find out what it will take
  • If it's urgent, say so

Replies come from a person. By sending, you authorize us to email you back. No marketing.