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

@highland-farm/simple-quagga

v0.1.3

Published

Barcode scanner with sane defaults and lightweight interface, built on quagga2.

Downloads

6

Readme

Simple Quagga Barcode Scanner

Barcode scanner with sane defaults and lightweight interface, built on quagga2. Interfaces are not complete or final, but it is functional. Since quagga2 comes bundled it is included as a devDependency only.

Look in examples to see how to use in browser as an iife script or esm module. Can also be used as a dependency when bundling for a lib or app. Uses snowpack for development and esbuild for transpiling/bundling/minifying.

Package folders:

  • /types : TypeScript definitions
  • /dist : ESM & IIFE browser bundles
  • /lib : ESM module unbundled

NPM scripts:

  • npm start to start snowpack dev server & launch examples in browser w/HMR for development
  • npm run build to transpile to ./lib, check/write TS type declarations to ./types, & bundle esm/iife w/working examples folder to ./dist
  • npm run lint to check linting rules; also run as part of build (but not git hooks for now)
  • npm run pretty:check to check Prettier rules; not run automatically for now
  • npm run pretty to apply Prettier rules; not run automatically for now

115135950-49331d80-9fd1-11eb-988b-5705bad3dc14

Working on:

  1. Actually read the TypeScript handbook and fix naïve or uninformed design choices

Backlog:

  1. Torch (flashlight) and zoom support for devices that support it
  2. Beeeeeeeeeeep. Beep
  3. Better scan quality checks (code component error thresholds) without custom format validator
  4. Decide if builder/options pattern is a good idea for init
  5. Testing, UTs, etc (you know, maybe... eventually)
  6. Intelligent selection of resolution and other options via MediaDevices.getSupportedConstraints()
  7. Camera device selection via MediaDevices.enumerateDevices()
  8. Check digit validation for code formats that support it
  9. Expose more Quagga config options
  10. Github actions to build, test, and publish
  11. QR codes (via quagg2-reader-qr or other)
  12. Possibly look into fixing Web Workers upstream

Done:

  1. ~~Eslint and consistent formatting~~
  2. ~~Bundle: Snowpack? Rollup? Just not browserify~~
  3. ~~Something other than python to server for local testing~~
  4. ~~Consume Quagga2 without passing through dependencies to consumers of this wrapper~~
  5. ~~Consider moving TS type declarations to a separate folder~~
  6. ~~Blob handling for passing back captured video frames and overlays~~
  7. ~~Make repo public and push alpha version to npmjs~~