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

cheddar-lang

v1.0.5

Published

The language that works for you

Downloads

15

Readme

Developing

Development for cheddar is described in detail on the docs. But first, to clone the cheddar repository, use the following:

$ git clone --recursive https://github.com/cheddar-lang/Cheddar.git

Additionally, when syncinc your branch with the latest update to develop, use the following command to avoid merge commmits:

$ git rebase develop -X theirs

Once your changes are ready to merge, submit a PR to the develop branch where it'll be reviewed and then merged if applicable

Manual Installation

Manual installation is simple. The only dependencies you must have are git and nodejs + npm. Additionally you should have make (preferably GNU), but this comes by default on almost every *nix system.

  • First, refer to the "Development" section for cloning the Cheddar repository.

  • The next step is to install the dependencies with npm. An automatic build should trigger if dependencies are installed succesfully. Once this command is finished you should see a dist/ directory created. If you don't, look for any errors in the installation.

$ npm install
  • Manually building / testing

You can use make to run the build, test, and install tasks:

$ make         # Production Build
$ make build   # Development Build
$ make test    # Run tests
  • Installing.

If you want to install the Cheddar CLI, you have some options. If you are doing a production installation, use make install. For all other cases use ./bin/install; with this you can pass a --method argument to specify whether you'd like to install for yourself (--method=alias) or for everyone on your computer (--method=path, the default) which may require elevated privileges. With --method=alias, provide the location of your bashrc file or equivalent with the --rcloc flag (usually for *nix systems this is ~/.bashrc, and for Mac this is ~/.bash_profile). You may specify the installation path with --method=path, Cheddar installs the binary in <path>/bin/cheddar and <path>/share/cheddar; this defaults to /usr/local.