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 🙏

© 2025 – Pkg Stats / Ryan Hefner

local-id-scan-journey

v2.0.8

Published

A React component for GBG ID verification and document scanning with bundled SDK

Readme

Local ID Scan Journey

A React component for GBG ID verification and document scanning with bundled SDK files.

Installation

npm install local-id-scan-journey

TypeScript Support

This package includes full TypeScript declarations. After installation, you should be able to import and use the component with full type safety:

import { LocalIdScanJourney, IdScanJourneyProps } from "local-id-scan-journey";

SDK Files Setup

The package includes GBG SDK files that need to be available in your project's public directory.

Automatic Setup (Recommended)

The package includes a postinstall script that automatically copies SDK files to your public directory. If this doesn't work automatically, you can run:

npx local-id-scan-journey/scripts/postinstall.js

Or using the npm script:

npm run copy-sdk --prefix node_modules/local-id-scan-journey

Manual Setup

If automatic setup fails, manually copy these files from node_modules/local-id-scan-journey/dist/ to your public/ directory:

  • idesmicro_asm.wasm
  • idesmicro_asm.js
  • Any vendor.*.js files
  • Any idscan-jcs-*.js files
  • Any ides-micro.*.js files

Usage

import React from "react";
import { LocalIdScanJourney } from "local-id-scan-journey";

function App() {
  const handleScanComplete = (result: any) => {
    console.log("Scan completed:", result);
  };

  return (
    <div className="App">
      <LocalIdScanJourney
        onScanComplete={handleScanComplete}
        // ... other props
      />
    </div>
  );
}

export default App;

Troubleshooting

TypeScript Declaration Issues

If you see errors like:

Could not find a declaration file for module 'local-id-scan-journey'
  1. Ensure you're using the latest version of the package
  2. Check that dist/index.d.ts exists in node_modules/local-id-scan-journey/
  3. Try clearing your TypeScript cache and rebuilding:
    rm -rf node_modules/.cache
    npm run build

SDK File Loading Errors

If you see errors like:

Failed to load script: /vendor.axios.*.js
  1. Run the SDK copy script manually:

    npx local-id-scan-journey/scripts/postinstall.js
  2. Verify the files exist in your public/ directory

  3. Check your build process isn't excluding these files

Next.js Configuration

For Next.js projects, you may need to add SDK files to your next.config.js:

/** @type {import('next').NextConfig} */
const nextConfig = {
  webpack: (config) => {
    config.resolve.fallback = {
      ...config.resolve.fallback,
      fs: false,
    };
    return config;
  },
  // Ensure public files are served correctly
  async rewrites() {
    return [
      {
        source: "/idesmicro_asm.wasm",
        destination: "/idesmicro_asm.wasm",
      },
    ];
  },
};

module.exports = nextConfig;

Development

To rebuild the package:

npm run build

To watch for changes:

npm run dev

License

MIT