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

pin-defines

v0.0.2

Published

Generate a header file with useful macros for AVR development

Readme

pin-defines

This small utility generates a header file for AVR projects with a bunch of macros to help with general IO.

Installation

npm install -g pin-defines

Usage

You will need: an input file. The default path is src/pins.yaml. It looks something like this:

---
  led: 2
  btn: 3

Here, you are defining that "led" is on pin 2 of the AVR, and "btn" is on pin 3. Next, run: pin-defines --device attiny85 --out-to-stdout. A header file will be output to your terminal.

You can also define --out to output to a file (default: src/pins.h) and --in to specify an alternate input file.

Don't forget to include your header file in your project.

The macros

Say you define "led" on pin 2 of an ATTiny85. You'll get output that looks something like this.

#define LED_DDR        DDRB
#define LED_PORT       PORTB
#define LED_PIN        PINB
#define LED_MASK       (1 << 2)

#define LED_ToOutput() LED_DDR |= LED_MASK
#define LED_ToInput()  LED_DDR &= ~LED_MASK

#define LED_High()     LED_PORT |= LED_MASK
#define LED_Low()      LED_PORT &= ~LED_MASK

#define LED_Read()     LED_PIN & LED_MASK
#define LED_IsLow()    !LED_Read()
#define LED_IsHigh()   LED_Read()

#define LED_LoopUntilHigh() do { } while (LED_IsLow())
#define LED_LoopUntilLow()  do { } while (LED_IsHigh())

Adding new devices

Create a new yaml file in src/devices following the structure of an existing device file, then add it to map.yaml (this is needed because multiple AVRs share the same pinout).

Pull requests welcome.