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

strand-core

v3.0.1

Published

Basic narrative engine core inspired by Twine

Downloads

10

Readme

strand

strand icon

Basic narrative scripting + interpreter inspired by Twine

npm i strand-core

language

note: anywhere JS appears here, it is embedded javascript to be evaluated in the context of the interpreter instance.

  • ::string: Marks the beginning of a passage with the title string. Between this line and the next passage title/EOF will be the body of the passage.
  • [[string|JS]]: Creates an action node with the text string and action JS. Expected use for this is to create buttons, links, etc and have the renderer tell the interpreter to evaluate the action on click
  • <<do JS>>: Evaluates JS when the passage is executed
  • <<if JS>><<elseif JS>><<endif>>: Evaluates JS inside the "if". If it evaluates to a truthy value, execution will continue along that branch and the rest will be ignored. If it evaluates to a falsey value, the same is repeated for each "elseif".
  • <<print JS>>: Evaluates JS when the passage is executed, and creates a text node with the evaluated value
  • anything else: Creates a text node

shorthands

  • [[link]]: Shorthand for [[link|this.goto("link")]]
  • [[link>target]]: Shorthand for [[link|this.goto("target")]]
  • > or >string: Shorthand for a "passage break", i.e. adds a link with the text string and an automatically generated passage heading. Expected use for this is breaking up long passages into multiple purely linear interactions without needing to mark up each one individually
  • >a|b|c: Same as above, but creates multiple links split by | that all link to the same automatically generated passage
  • <<set var=val>>: Shorthand for <<do this.var=val>>
  • <<else>>: Shorthand for <<elseif true>>

VSCode extension

Example renderer

example

::start
some text with a [[shorthand link]] and a longform [[action|this.goto("other passage")]]

::shorthand link
<<set linkClicked=true>>this passage appears when you click the link
[[back|this.back()]]

::other passage
<<if this.linkClicked>>
this text shows up if you visited the shorthand link passage before getting here
<<else>>
this text shows up if you didn't
<<endif>>