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

scenarioscript

v1.0.1

Published

Script language suitable for storing scenario data.

Downloads

2

Readme

ScenarioScript v1.0.1

Script language suitable for storing scenario data.

Example

[Wife]     Have you got anything without spam?
[Waitress] Well, there's spam egg sausage and spam, that's not got much spam in it.
[Wife]     I don't want ANY spam!
[Man]      Why can't she have egg bacon spam and sausage?
[Wife]     THAT'S got spam in it!
[Man]      Hasn't got as much spam in it as spam egg sausage and spam, has it?
[Vikings]  Spam spam spam spam... (singing, repeat=10)

This is parsed to the following:

[{
  "type": "message",
  "role": "Wife",
  "message": "Have you got anything without spam?",
  "params": {}
}, {
  "type": "message",
  "role": "Waitress",
  "message": "Well, there's spam egg sausage and spam, that's not got much spam in it.",
  "params": {}
}, {
  "type": "message",
  "role": "Wife",
  "message": "I don't want ANY spam!",
  "params": {}
}, {
  "type": "message",
  "role": "Man",
  "message": "Why can't she have egg bacon spam and sausage?",
  "params": {}
}, {
  "type": "message",
  "role": "Wife",
  "message": "THAT'S got spam in it!",
  "params": {}
}, {
  "type": "message",
  "role": "Man",
  "message": "Hasn't got as much spam in it as spam egg sausage and spam, has it?",
  "params": {}
}, {
  "type": "message",
  "role": "Vikings",
  "message": "Spam spam spam spam...",
  "params": {
    "singing": true,
    "repeat": 10
  }
}]

Rules

Basic Rules

  • Empty lines means nothing.
  • There are 2 types of lines: Message and Separator
    • A separator line looks like ---. Separators are lines which contains only dashes.
    • A message line typically looks like [name] message (key=value, ...). See below for details.

Message

Example:

[Vikings]  Spam spam spam spam... (singing, repeat=10)

The initial part [Vikings] is the role of the line. In this case the role of the line is Vikings. The valid characters for the names for roles are anything except ].

The last part (singing, repeat=10) is the parameters of the line. In this case the parameter is equivalent as the json object:

{
  "singing": true,
  "repeat": 10
}

The parameters are the comma-separated sequence of key=value. The =value part is optional and if it's omitted, it means true. If the value looks like a number, then it's considered as a number. If the value looks like a boolean, then it's considered as a boolean. Otherwise it's a string.

Role can be omitted. Example:

There was a light at first

In this case, the role of the line is null and the whole line is message of the line.

Separator

A separator line only has '-' in it.

Example:

[ Jonathan ] How many have you killed?
[ Dio ] Do you remember how many breads you've eaten in your life?
---
[ Jonathan ] I never forgive you, Dio.
[ Dio ] Haha.

The --- line above is a separator line.

Note:

  • Any line except separator is a message line.
  • There's no syntax error. Any string is valid.

Parser package

Install

npm install scenarioscript

Usage

const parser = require('scenarioscript')

parser.parse(`
[Wife]     Have you got anything without spam?
[Waitress] Well, there's spam egg sausage and spam, that's not got much spam in it.
[Wife]     I don't want ANY spam!
[Man]      Why can't she have egg bacon spam and sausage?
[Wife]     THAT'S got spam in it!
[Man]      Hasn't got as much spam in it as spam egg sausage and spam, has it?
[Vikings]  Spam spam spam spam... (singing, repeat=10)
---
`) /* =>

[{
  "type": "message",
  "role": "Wife",
  "message": "Have you got anything without spam?",
  "params": {}
}, {
  "type": "message",
  "role": "Waitress",
  "message": "Well, there's spam egg sausage and spam, that's not got much spam in it.",
  "params": {}
}, {
  "type": "message",
  "role": "Wife",
  "message": "I don't want ANY spam!",
  "params": {}
}, {
  "type": "message",
  "role": "Man",
  "message": "Why can't she have egg bacon spam and sausage?",
  "params": {}
}, {
  "type": "message",
  "role": "Wife",
  "message": "THAT'S got spam in it!",
  "params": {}
}, {
  "type": "message",
  "role": "Man",
  "message": "Hasn't got as much spam in it as spam egg sausage and spam, has it?",
  "params": {}
}, {
  "type": "message",
  "role": "Vikings",
  "message": "Spam spam spam spam...",
  "params": {
    "singing": true,
    "repeat": 10
  }
}]

*/

API

const parser = require('scenarioscript')

parser.parse(script)

  • @param {string} script The script
  • @return {object}

This parses the ScenarioScript and returns the parsed object representation.

License

MIT