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

inklecate

v1.8.1

Published

A tiny wrapper around the desktop executables for ink's command-line Ink language compiler.

Downloads

36

Readme

inklecate

Install with npm i -D inklecate.

This package is a wrapper around Inkle's inklecate tool for compiling and playing Ink stories. It will not compile for client-side execution in a browser.

There are some differences between inklecate and this package. One major difference is this library allows output to be cached and deleted automatically, then emitted over stdout from the CLI, or returned from the function if using the library. Logging is performed of errors, warnings, and author notes if a outputFilepath argument is provided. Otherwise, all these log items will be stored in the compilerOutput property of the returned object.

The inklecate binaries were written solely by Inkle and this package is released under the same license as Ink. That license is MIT at the time of this writing, but if it changes, the license of this package should be considered to follow it.

How to use

The inklecate package can be used either as the inklecate export of the module and as a command-line app.

CLI options:

  inklecate <options> ...<ink file(s)>

  -o, --outputFile <outputFile>: Output file name.
  -c: Count all visits to knots, stitches and weave points, not just those referenced by TURNS_SINCE and read counts.
  --verbose: Verbose mode - print compilation timings.
  --DEBUG: Enable debug logging for inklecate-node.

The arguments for the module's inklecate function:

function inklecate(args: {
  countAllVisits?: boolean;
  outputFilepath?: string;
  inputFilepath?: string;
}): Promise<InklecateReturn>;

The single positional argument is the input filepath.

If the output filepath argument is not provided, the file will be generated in a cache location and output as plain text JSON (in CLI mode) or a plain JavaScript object (as a node module).

Other notes