open-index/open-npm huggingface dataset:
npm package: @highland-farm/simple-quagga
Description: Barcode scanner with sane defaults and lightweight interface, built on quagga2.
Author: Josh Storz
Latest version: 0.1.3

# 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](https://user-images.githubusercontent.com/72341/117096800-ee166000-ad1e-11eb-94ff-b2cd4dec9204.png)

Working on:

1. Actually read the TypeScript handbook and fix na&#239;ve or uninformed design choices

Backlog:

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

Done:

1. ~~Eslint and consistent formatting~~
1. ~~Bundle: Snowpack? Rollup? Just not browserify~~
1. ~~Something other than python to server for local testing~~
1. ~~Consume Quagga2 without passing through dependencies to consumers of this wrapper~~
1. ~~Consider moving TS type declarations to a separate folder~~
1. ~~Blob handling for passing back captured video frames and overlays~~
1. ~~Make repo public and push alpha version to npmjs~~
npm package: @highlandertech/eslint-config
Description: HighlanderTech ESlint Config
Author: Giovani Franz
Latest version: 2.0.6

# HighlanderTech ESLint config

## Whats included?

- Standard config base;
- React plugin;
- React Hooks plugin;
- JSX a11y plugin;
- Airbnb
- Simple Import Sort
- Prettier;

## Setup

1. Install the dependencies
```
npm i -D eslint @highlandertech/eslint-config
```

2. Create a `.eslintrc.json` file extending the config:
```
{
  "extends": "@highlandertech/eslint-config/eslint"
}
```
> You can also use a `.eslintrc.js` instead of JSON if you prefer.

3. Create a `.prettierrc.js` file extending the config:
```
{
  module.exports = require("@highlandertech/eslint-config/prettier")
}
```
npm package: @highlandertech/use-translate
Description: useTranslate Hook React HighlanderTech 
Author: giovanifranz
Latest version: 0.1.5

# HighlanderTech useTranslate Hook

## Installation

```sh
npm install @highlandertech/use-translate
```

## Example

```typescript
import { LanguageProvider } from '@highlandertech/use-translate';
import React from 'react';
import ReactDOM from 'react-dom';
import App from './App';

ReactDOM.render(
  <React.StrictMode>
    <LanguageProvider>
      <App />
    </LanguageProvider>
  </React.StrictMode>,
  document.getElementById('root'),
);
```


```typescript
import React, { useCallback } from 'react';
import { useLanguage, useTranslate } from '@highlandertech/use-translate';
import type {
  Language,
  DifferentTextsInput,
} from '@highlandertech/use-translate';

type Text = {
  title: string;
  description: string;
};

const data: DifferentTextsInput<Text> = {
  portuguese: { title: 'Olá Mundo', description: 'Esse é o hook useTranslate' },
  english: {
    title: 'Hello World',
    description: 'This is the useTranslate hook',
  },
};

const currentLanguageText = {
  portuguese: 'Você está usando Português',
  english: 'You are using English',
};

function App() {
  const { language, toggleLanguage } = useLanguage();
  const { title, description } = useTranslate({ textsInput: data, language });
  const currently = useTranslate({ textsInput: currentLanguageText, language });

  const handleClick = useCallback(
    (lang: Language) => toggleLanguage(lang),
    [toggleLanguage],
  );

  return (
    <>
      <h1>{title}</h1>
      <h2>{description}</h2>
      <button onClick={() => handleClick('english')}>English</button>
      <button onClick={() => handleClick('portuguese')}>Portuguese</button>
      <p>{currently}</p>
    </>
  );
}

export default App;

```

## Demo

https://fantastic-pixie-538075.netlify.app/

## Developer

| [<img src="https://avatars.githubusercontent.com/u/79429654?v=4" width="75px;"/>](https://github.com/giovanifranz) |
| :-: |
|[Linkedin](https://www.linkedin.com/in/giovanifranz)|
|[Email](mailto:giovanifranz151@gmail.com)|
npm package: @highlands/highlands-ui
Description: React components based on material-ui.
Author: Church of the Highlands
Latest version: 1.0.1

# @highlands/highlands-ui

React components based on material-ui.

## Installation

Install the package in your project directory with:

```sh
// with npm
npm install @highlands/highlands-ui

// with yarn
yarn add @highlands/highlands-ui
```

## Documentation

[The documentation](https://material-ui.com/)
npm package: @highlands/highlands-ui-icons
Description: Highlands Svg Icons converted React components.
Author: Church of the Highlands
Latest version: 1.0.2

# @highlands/highlands-ui-icons

Highlands Svg Icons converted React components.

## Installation

Install the package in your project directory with:

```sh
// with npm
npm install @highlands/highlands-ui-icons

// with yarn
yarn add @highlands/highlands-ui-icons
```
npm package: @highlandsolutions/eslint-config-highland
Description: Highland's ESLint config
Author: Curtis Blackwell
Latest version: 1.0.1

# eslint-config-highland
This package provides two ESLint configs: one for general JavaScript (the default) and one for Vue CLI setups.


## Installation
```sh
npm i -D @highlandsolutions/eslint-config-highland
```


## Usage
To use the default config, you need only place `extends: '@highlandsolutions/highland',` in your ESLint config. To use the Vue CLI config: `extends: '@highlandsolutions/highland/lib/vue-cli',`
npm package: @highlight-ai/app-runtime
Description: Developer facing app runtime for Highlight
Latest version: 0.3.9

This package provides types for the Highlight runtime API. Highlight is an app platform for AI apps that allows you to quickly build context aware apps. For example, you could use the runtime API to build a task list app that automatically assembles tasks based on your screen contents.

Learn more about Highlight at our website: [https://highlight.ing](https://highlight.ing).

## Using the Runtime

Please read over the [developer documentation for the runtime API](https://docs.highlight.ing/learn/developers/runtime-api) to get started.

You can access the TypeDoc for this library [here](https://highlight-ing.github.io/highlight/app-runtime/).

Under the hood, this library just accesses the Highlight runtime API via the `globalThis.highlight` object. This object will only be available when running inside of the Highlight app. All methods will throw an Error if you attempt to call them from outside of Highlight.

## Contributing

We currently do not accept contributions to this package, this package is maintained by the Highlight team. However, feel free to [join our Discord](https://discord.gg/hlai) if you have any questions or feedback. We are welcome to discuss any ideas you have.

## License

This NPM library is licensed under the MIT license.
npm package: @highlight-ing/electron-app-universal-protocol-client
Description: Unified cross-platform protocol handler for Electron apps, supporting development environments.
Latest version: 1.3.0

# About

Unified and simplified API for Electron application's protocol handlers ("deep links").

Features:
- support for all platforms (Windows, macOS and Linux)
- development mode
- capturing start-up request (if application was not running and protocol request caused it to be started)

## electron-deeplink

This package is based on [electron-deeplink](https://github.com/glawson/electron-deeplink).

Differences:
- switch to `yarn`
- support for prebuilds (via `prebuildify` and GitHub Actions)
- types support for `on('request')`
- no need to call the API as early as possible to catch the first request (just require it)
- no need to create a new instance of class to use the API
- removed a lot of default behavior (like focusing the window after protocol request)
- removed logging support
- minor fixes

Further changes are listed in [CHANGELOG.md](./CHANGELOG.md).

Huge thanks for @glawson for creating `electron-deeplink` and allowing me to continue his work as recommended fork.

# Installation

```sh
# If you use npm:
npm install electron-app-universal-protocol-client

# If you use yarn:
$ yarn add electron-app-universal-protocol-client
```

# Usage

## API

### `electronAppUniversalProtocolClient.on('request', requestHandler)`

Register handler for protocol requests in your application.

```js
electronAppUniversalProtocolClient.on(
  'request',
  async (requestUrl) => {
    // Handle the request
  },
);
```

### `electronAppUniversalProtocolClient.initialize({ protocol: string; mode?: 'development' | 'production' })`

Initialize the client.

`mode` is `'production'` by default.

**Remember to register protocol handlers before calling `initialize`, otherwise you might lose some requests.**

```js
await electronAppUniversalProtocolClient.initialize({
  protocol: 'your-app-id',
  mode: 'development', // Make sure to use 'production' when script is executed in bundled app
});
```

## [Example](./example/main.js)

Please note that example directory contains fake `node_modules` that allows the example to be started within this repository.

# Development mode

Make sure you're launching Electron with your **main script path** as first argument. Development mode is implemented upon this assumption.

# macOS Development Mode Permissions Issue

Due to macOS permissions system, you could experience following errors after starting your Electron app in development mode:
```
[42590:1203/200159.650790:ERROR:mach_port_rendezvous.cc(310)] bootstrap_look_up com.github.my-app-id.MachPortRendezvousServer.42588: Permission denied (1100)
[42590:1203/200159.651421:ERROR:child_thread_impl.cc(228)] Mach rendezvous failed, terminating process (parent died?)
```

To fix them, run this command in project's root directory:
```
sudo xattr -r -d com.apple.quarantine ./
```