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

eatme

v0.0.2

Published

Code Examples in Wonderland

Downloads

5

Readme

EatMe

Code Examples in Wonderland

Synopsis

In Markdown, write a code example like this:

```yaml-to-json
name: Alice
place: Wonderland
```

It renders like this:

...

Click on it and it turns into this:

...

Description

In online documentation, all code examples in that involve inputs and outputs should be interactive. It should be trivial for a documentation author to create interactive examples. The interactive layouts should be completely and easily configurable.

EatMe is a project to make this a reality.

Let's say you configure EatMe like this:

coffee-js:
- name: CoffeeScript
  type: input
- name: JavaScript
  from: CoffeeScript
  func: compileCoffee

When you write an example like:

```coffee-js
alert "I'm #{if ok() then '' else 'not '}ok!"
```

You see the CoffeeScript code and the JavaScript it compiles to as a nicely formatted example. When you click on it, the CoffeeScript becomes editable so that you can try out variations.

This is actually how the CoffeeScript website examples work. But with EatMe, everything is configurable and easily embeddable into lots of documentation layouts.

Fiddle, CodePen and CodeSandbox let you create examples for HTML/JS/CSS on their sites.

EatMe can be configured to make those kind of examples inline in your docs or web pages. But it can also be configured in any arrangement imaginable, with any kinds of inputs and outputs.