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

@ovhcloud/ods-recipes

v19.7.1

Published

ODS Recipes

Readme

ODS Recipes

Create a new recipe

From the root of the design-system project, run the following:

yarn new:recipe

Then follow the prompt.

Repository structure

When working on a recipe, you'll have your own small project to work with located under ods-recipes/src/components/<your-component>.

You should not update any files outside of this directory.

Commands

In your component directory, you have access to the following commands:

  • yarn start: start a development storybook that you can use to implement your recipe
  • yarn lint:css: run the linter rules regarding CSS files (if any)
  • yarn lint:scss: run the linter rules regarding SCSS files (if any)
  • yarn lint:ts: run the linter rules regarding TS files

Folders

Implementation directories

You'll mainly work under the src directory under which you'll find one or more implementation directory, depending on the configuration you choose during the init script prompt (by default you should at least see a css-modules directory).

Each contains an index.tsx file where you should start writing your recipe code .

Please implement each of those directories before submitting any recipe.

The css-modules implementation is mandatory and should not be bypassed.

Dev stories

The file dev.stories.tsx contains all the test frames that will be rendered on the development storybook when running yarn start.

Use this file as you please to create as many use case that you need to validate your recipe.

Example of two stories:

export const Default = () => (
  <MyComponent.CssModule />
);

export const Disabled = () => (
  <MyComponent.CssModule disabled />
);

index.ts

The file index.ts contains the metadata of the recipe (used by our documentation system), when adding a new recipe you'll have to define the right SEARCH_TAG tags for the recipe (you can leave the rest untouched).

In case, you think a tag is missing for your use case, feel free to add it to the enum list in ods-recipes/src/constants/search-tag.ts (if you have any doubt about how relevant the tag may be, feel free to contact us).

Validation workflow

When all implementations for your recipe are done, please run locally the linter commands and fix any possible errors.

You can then submit a Pull Request under the ODS repository. We'll review it as soon as possible.