Solid Primitives is a project dedicated to building high-quality, community-contributed primitives for Solid 2.0. Every utility is thoroughly tested, continuously maintained, and reviewed against a consistent quality bar before it lands in the repository. Our aim is to extend Solid's primary and secondary primitives with a well-rounded set of tertiary primitives. While Solid Primitives isn't officially maintained by the SolidJS Core Team, it's managed by members of the SolidJS core and ecosystem teams. This separation lets the core library iterate independently while keeping Solid Primitives in sync with where Solid is headed.
Visit https://primitives.solidjs.community for documentation and demos for each primitive.
Solid Primitives wraps client- and server-side functionality in a fully reactive API layer. The more deeply rooted these tertiary primitives become, the more they serve as a foundation within Solid's broader ecosystem. Building on well-tested, widely reused foundations makes the applications built on top of them smaller (through aggregate tree-shaking), more readable (through concise, consistent APIs), and more stable (through managed testing and maintenance).
The next branch and all packages published under the next dist-tag target Solid.js 2.0 (solid-js@^2.0.0). Solid 2.0 introduces a new async reactivity model, updated control-flow primitives, and breaking API changes that affect every package in this library.
Every package in this release has been migrated to the new 2.0 APIs and is incompatible with Solid 1.x, with two exceptions: fetch and resource still target Solid 1.x. See the migration guide for what changed in each package. If you are still on Solid 1.x, use the latest stable releases from the main branch.
- Async reactivity — primitives that previously returned
Resourceor usedcreateResourceinternally now expose plain signal accessors that throwNotReadyErroron pending state, integrating with<Loading>and<Errored>boundaries. use:directives removed — directive-based APIs (e.g.use:fileUploader) have been replaced with ref callback factories (ref={fileUploader(opts)}).isServerimport path — moved fromsolid-js/webto@solidjs/web.- Split effects — all
createEffectcalls use the Solid 2.0 two-argument compute/apply form to avoid stale reads. - Peer dependencies — migrated packages require
solid-js@^2.0.0and@solidjs/web@^2.0.0.
See the migration guide and the CHANGELOG of each individual package for a full list of breaking changes.
The @solid-primitives/utils package provides shared helpers used across the library.
Each package exposes its raw TypeScript source via a custom @solid-primitives/source export condition. This lets tests, the playground, and cross-package imports inside the monorepo resolve directly to .ts files without a build step, while external consumers always receive the compiled dist/ output.
See EXPORTS.md for a full explanation of how this works and why we use it.
Contributions are what make this project possible. Solid Primitives welcomes pull requests, bug reports, and feature proposals from the community.
Please read CONTRIBUTING.md for details on the submission process, coding standards, and the stage-based review pipeline all new primitives go through before acceptance.
If you discover a security vulnerability, please follow the process outlined in SECURITY.md rather than opening a public issue.
Solid Primitives is released under the MIT License. Copyright © 2021 Solid Core Team.
Each package is independently licensed — see the LICENSE file within any package directory for its specific terms.
Solid Primitives is owned and maintained by the Solid Primitives Working Group — a group of volunteers drawn from the Solid core and ecosystem teams. While not an officially supported product of the Solid Core Team, the working group coordinates directly with core maintainers to ensure primitives remain aligned with the direction of the framework.
Decisions about new packages, stage promotions, and breaking changes are made collaboratively by working group members. To get involved or follow along, join the SolidJS Discord (#solid-primitives channel) or open a discussion in this repository.
Built with ❤️ by the Solid Community