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

global-gateway-image-capture-web-sdk-test

v4.0.23

Published

Image capture web SDK

Readme

GlobalGateway Image Capture Web SDK

This sample app contains the Acuant SDK with the HTML Sample App wrapper.

This README document is for developers only and will get removed automatically when prepping the sample app for production release.

Dev environment setup

Inside the repo root directory:

  1. Create .env file:
  • cp .env.template .env to create a new .env file with this content:
SDK_USERNAME=                   // Acuant SDK username credential
SDK_PASSWORD=                   // Acuant SDK password credential
PORT=                           // Port on which to run the application. If blank, the port will default to 3000
ARTIFACTORY_DEVOPS_USER=        // JFrog username
ARTIFACTORY_DEVOPS_PASSWORD=    // JFrog password
NPM_TOKEN=                      // NPM token for nexus.rnd-trulioo.com/repository/npm-private
  1. Apply credentials to demo app:
  • After adding the credentials, run export $(cat .env)
  • Then run the following commands:
sed -i -e "s|USERNAME_TO_REPLACE|$SDK_USERNAME|gi;s|PASSWORD_TO_REPLACE|$SDK_PASSWORD|gi" src-demo/app.ts

You should now see the change in src-demo/app.ts at username and password.

  1. Install dependencies and Acuant SDK:
yarn install
  1. Start local development of demo app:
yarn dev --port <xxxx>
  • dev server port defaults to 3000 if no --port specified
Build

Build for production:

yarn build

which includes:

  • yarn build:dist -- build distribution files
  • yarn build:lib -- build JS files for npm packaging
  • yarn build:types -- build definition files for npm packaging

Build for development:

yarn build:dev

Similar to yarn build but without production flag, the dist/ would include non-minified and sourcemap details.

Utils

Clean up built files/assets:

yarn clean

Lint code in src and src-demo:

yarn lint

Apply code formatting for src and src-demo:

yarn format
Test

Run unit tests:

yarn test

which runs all tests in __tests__/ with pattern *.test.ts|js.

Run distribution

There are two options to run distribution build on your local machine and with docker.

Prerequisite: step '1. Create .env file' of section Dev environment setup.

Run on local machine

yarn install
yarn build
export $(cat .env)
./scripts/populateAcuantCredentials.sh
yarn start

Browse the output url, http://localhost:8080 by default.

Run with docker

docker-compose build
docker-compose up

Browse the output url, http://localhost:3000 by default.