npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@case-framework/survey-ui

v0.2.4

Published

React UI components for CASE surveys, including the `SurveyEditor`.

Readme

@case-framework/survey-ui

React UI components for CASE surveys, including the SurveyEditor.

SurveyEditor styling in a host project

Import the package stylesheet once in your app entry point:

import "@case-framework/survey-ui/css";

If you only want the editor's default variable values as a tiny standalone asset, import:

import "@case-framework/survey-ui/editor-defaults.css";

@case-framework/survey-ui/css already includes these defaults, so the standalone file is only needed when the host wants a separate variables-only layer.

If the host app uses Tailwind CSS v4, add the package as a source in the host global CSS file so Tailwind also scans the editor package:

@import "tailwindcss";
@source "../node_modules/@case-framework/survey-ui/dist";

Override the editor-specific CSS variables on the .survey-editor scope in the host stylesheet:

.survey-editor {
  --main-bg-color: oklch(98.5% 0 0);
  --main-bg-dot-color: oklch(85% 0 0);
  --main-bg-dot-grid-size: calc(var(--spacing, 0.25rem) * 5);

  --footer-bg-color: oklch(37.3% 0.034 259.733);
  --footer-text-color: oklch(98.5% 0 0);
  --footer-height: calc(var(--spacing, 0.25rem) * 6);
}

Available editor-scoped variables:

  • --main-bg-color
  • --main-bg-dot-color
  • --main-bg-dot-grid-size
  • --footer-bg-color
  • --footer-text-color
  • --footer-height

The editor also uses the shared UI theme tokens from the package stylesheet, so you can override variables such as --background, --foreground, --card, --primary, --muted, --accent, --border, --input, and --ring if you want the rest of the editor chrome to match your host theme.