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 🙏

© 2024 – Pkg Stats / Ryan Hefner

jsonrecipe-schema

v0.0.2

Published

A JSON schema for culinary recipes.

Downloads

5

Readme

JSON Recipe

This project intends to provide a standard way to store (culinary) recipe information in JSON format. Its (admittedly ambitious) goal is to be simple enough for quick creation of recipes yet expansive and precise enough to provide a reasonably complete machine-readable description.

Ingredient format

Each ingredient in the ingredient list may be either a single string or an object. The advantage of the string format is that it is considerably easier to read and write for a human; the advantage of the object format is the same, but for a computer. A sample ingredient in the object format is as follows:

{
  "quantity": 2,
  "unit": "cup",
  "item": "water",
  "preparation": "boiled"
}

The quantity can also be a fractional number; using floating point values such as 1.1 is not allowed.

{
  "quantity": "1 1/4",
  "unit": "tablespoon",
  "item": "brown sugar"
}

TODO: more thoroughly describe the components.

In string format, the above two examples would be

"2 cups water, boiled"

and

"1 1/4 tablespoons brown sugar"

Thus, in terms of the components of the object format, the string format is

<quantity> <unit> <item>[, preparation]*

Note that the unit "each" must be explicitly provided in the string format where desired; it is only correct to write "1 each red pepper", not "1 red pepper". On the contrary, the object format allows the omission of the unit key to imply "unit": "each".

TODO: write a formal grammar and expand on some of the additional cases to consider. Give an example of a case that might not be correctly handled by the string format that must be expressed in object format (or specify why this is impossible).