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

@sfstuebingen/curb

v1.5.0

Published

Common React components for SfS web UIs

Readme

React-utils

This is a Javascript library for building Web applications using React at the SfS. It contains generic components for rendering data into a concrete UI, and implements some conventions for styling those components. It also contains some utility functions that are useful in React projects.

Code structure

The code is grouped into directories by functionality. The directories under components contain React components; see the documentation in those directories for the components defined there.

In addition, there are several other files that contain code shared across the library:

  • errors.js: assorted error classes and handling functions
  • helpers.js: assorted common utility functions

Use

Installing the package

The library is available as a package on NPM in the @sfstuebingen scope. To install the package, run

npm install --save '@sfstuebingen/curb'

in the directory containing your node_modules directory. (For internal projects at the SfS, this is probably webui.)

The library is shipped as ES2015 source code only. Consuming applications are expected to include whatever code they need from the library via their own build process.

When you use this library in another project, that project should also have the following NPM packages installed:

  • react
  • seamless-immutable
  • classnames

These are listed as peer dependencies in the package.json file. This means that this package depends on them, but installing the package will not install them automatically. Instead, you must manually ensure that they are installed. Consuming applications (for instance, any project based on the SfS' reactprojecttemplate repository) are likely to depend on these packages already, so you may already have them installed in your project. Listing them as peer dependencies helps prevent multiple versions from being installed, which causes problems with React in particular.

Importing and using the components and other code

In general, you should just import the object you want using the full path within this package to the file where it is defined:

import { makeByIdReducer } from '@sfstuebingen/curb/helpers;

As a shortcut, you can import any React component from the library from @sfstuebingen/curb/components, so you can leave off the name of the directory containing the component:

import { Button, Card } from '@sfstuebingen/curb/components';