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

@mitodl/smoot-design

v6.25.0

Published

Design system components for MITODL Projects

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

mitx-devopsmitx-devopsrhysyngsunrhysyngsungumaercgumaerccchudzickicchudzickiabeglovaabeglova

Keywords

Readme

@mitodl/smoot-design

Design system components for MITODL Projects

NPM Version

NPM Last Update

NPM Unpacked Size

GitHub branch status

Development and Release

All PR titles and commits to main should use the conventional commits format. During release, the types of commits included since the last release inform what sort of version bump should be made. For example, bugfixes yield a new patch version, whereas breaking changes trigger a major version bump.

To trigger a release, use the "Releases (Semantic & Pre-release)" github action (release.md). This action will perform a semantic release or pre-release based on release-type input.

Pre-releases: The action will (1) publish the latest commit on specified branch to NPM, with a version v0.0.0-<git-short-sha>, e.g., v0.0.0-7bc0c0f; and (2) leave a comment on the branch's PR indicating releaseed version number, if such a PR is open.

Semantic Release: The action will:

  1. Inspect the commit history since previous release for conventional commits an
  2. Determine whether the version bump should be major, minor, or patch based on commit types. Breaking changes (e.g., feat!: remove Button variant 'outlined') will result in major version bumps.
  3. Publish the package to NPM and the repository's Github Releases.

Installation

Ensure peerDependencies are installed as well. See package.json.

Documentation

Documentation for smoot-design components is available at https://mitodl.github.io/smoot-design.

Storybook

Components in smoot-design are documented using Storybook's autodocs feature.

Autodocs should infer props and comments from Typescript + JSDoc comments. However, autodocs can be a bit finnicky. Tips:

  • Filename should match Component Name: If you're documenting Button, it must be exported from a file called Button.tsx.
  • Component displayName: Some components may need an explicit displayName, this can be set by Button.displayName="Button".
    • React component display names are not visible to end users; they are used in React's Dev Tools. React automatically adds display names for most components while transpiling, but autodocs uses un-transpiled code to generate documentation.