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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@tesseractjs/cli

v0.1.3

Published

Tesseract.js project management command line interface

Downloads

15

Readme

Getting Started

Prerequisites:

Install imagemagick:

brew install imagemagick

Install:

npm install -g @tesseractjs/cli
# OR
yarn global add @tesseractjs/cli

Provide config:

You can add wrapper.config.json (or any other JSON file, but then don't forget to specify its path by command line parameter --config) like this:

{
  "name": "TheAppName",
  "template": {
    "resources": {
      "appIcon": "./icon.png",
      "splashImage": "./splash-image.png"
    },
    "appId": {
      "ios": "test.app"
    }
  },
  "appConfig": {
    "dappUrls": {
      "default": [{
        "url": "https://demo.tesseract.one/",
        "name": "main"
      }],
      "testing": []
    },
    "rpcUrls": {
      "1": "https://mainnet.infura.io/v3/f20390fe230e46608572ac4378b70668"
    },
    "extra": {}
  }
}

and execute cli command

tesseract create wrapper -c "./config-name.json"

or use command line parameters

tesseract create wrapper TheAppName \
  --url "https://tesseract.one/" \
  --rpc "https://mainnet.infura.io/v3/f20390fe230e46608572ac4378b70668" \
  --app-id "test.app"

also, don't forget to provide icon and splash-image for the app

Configuration of wrapper

The final configuration will be a combination of config files and command line parameters

Command line parameters

| parameter | shortcut | Description | |---|---|---| --name | -n | Name of the app --url | -u | URL of the website for the app, if there is more than one URL use config file --rpc | -r | URL of Ethereum RPC, if there is more than one URL use config file --template | -t | Path to template for the wrapper, also can be a link on github repo --out | -o | Path to the output directory --pods | -p | Run pod install after generation or not --config | -c | Path to the configuration file --app-id | -i | Bundle and package id of aplication --help | -h | Auto-generated usage information --version | -v | Version of the CLI

Configuration file

{
  "name": "string",
  "outputDir": "string",
  "runPodInstall": "boolean",
  "template": {
    "path": "string",
    "resources": {
      "appIcon": "string",
      "splashImage": "string"
    },
    "fabric": {
      "key": "string",
      "secret": "string"
    },
    "appId": {
      "ios": "string"
    }
  },
  "appConfig": {
    "dappUrls": {
      "default": [{
        "url": "string",
        "name": "string"
      }],
      "testing": []
    },
    "rpcUrls": {
      "string": "string"
    },
    "extra": {}
  }
}

Template property

template needed only for a generation and won't be used by the app; path also can be an URL on github repo

AppConfig property

appConfig will be used by the app implicitly, notice that templates can require different properties (statusBarColor, isLightStatusBar, etc.), also you can add extra properties to the app