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

story-parser

v2.3.6

Published

A parser for interactive stories.

Downloads

13

Readme

story-parser

A parser for choose your own adventure stories with optional combat system

Story Parser uses parser combinators to turn a simple text format into a JavaScript object.

Example Story

The main parser expects a series of numbered pages with options that each point to the number of another page. The dashes that separate the pages are optional. Pages that end the story must be terminated with the END keyword.

Input text:

PAGE 0
"You are in a room, there is a door to the left and a door to the right.
It is a dark room."
OPTION 1
"Take the door on the left"
OPTION 2
"Take the door on the right"
OPTION 3
"Take the door at the end of the hall"
--------------------------------------
PAGE 3
"The hall ends in lava, you die!"
END
--------------------------------------
PAGE 1
"You are in an empty room."
OPTION 0
"Go back"
--------------------------------------
PAGE 2
"You are in a bright green field, you made it!"
END

Output JS:

{
  "type":"SIMPLE",
  "pages":[
    {
      "id":0,
      "text":"You are in a room, there is a door to the left and a door to the right.\nIt is a dark room.",
      "options":[
        {"target":1,"text":"Take the door on the left"},
        {"target":2,"text":"Take the door on the right"},
        {"target":3,"text":"Take the door at the end of the hall"}]
    },
    {
      "id":3,
      "text":"The hall ends in lava, you die!",
      "options":"END"
    },
    {
      "id":1,
      "text":"You are in an empty room.",
      "options":[
        {"target":0,"text":"Go back"}
        ]
    },
    {
      "id":2,
      "text":"You are in a bright green field, you made it!",
      "options":"END"
    }
  ]
}