open-index/open-npm huggingface dataset:
npm package: @hackolade/hck-esbuild-plugins-pack
Description: The pack of custom ESbuild plugins for packaging Hackolade plugins
Author: Hackolade
Latest version: 0.0.1

# hck-esbuild-plugins-pack
The pack of custom ESbuild plugins for packaging Hackolade plugins

## Contains
- **copyFolderFiles** - Plugin for copy files from folder where script executed to package folder. Support excluding files by extension or by file name.
- **addReleaseFlag** - Plugin for modifying package.json file by adding `release: true` flag

## Installation
```
npm install @hackolade/hck-esbuild-plugins-pack
```

## Usage
```javascript
import { build } from 'esbuild';
import { copyFolderFiles, addReleaseFlag } from '@hackolade/hck-esbuild-plugins-pack';

(async () => {
    const res = await build({
        entryPoints: ['./demo.js'],
        bundle: true,
        outfile: './dist/main.js',
        plugins: [
            copyFolderFiles({
                fromPath: __dirname,
                targetFolderPath: './dist',
                excludedExtensions: ['.js', '.g4'],
                excludedFiles: ['.github', 'package-lock.json'],
            }),
            addReleaseFlag('./dist/package.json'),
        ],
    });
})();
```
npm package: @hackolade/os-dns-native
Description: Re-published version to have all prebuilds defined as npm packages without platform constraints for cross building an Electron application - Perform DNS queries using OS APIs
Author: Anna Henningsen
Latest version: 27.1.0

# os-dns-native

Perform DNS queries using native OS APIs. Unlike the built-in `dns.resolve*`
family of functions, this module talks to the OS instead of performing UDP
queries.

Currently, A (IPv4), AAAA (IPv6), CNAME, TXT and SRV are supported.

The library exports match a subset of the Node.js `dns` module's. There is an
extra `.withNodeFallback` variant that allows using the OS methods with a
fallback to the Node.js methods if the former failed.

```js
import osDns from 'os-dns-native';
const addresses = await osDns.promises.resolve6('example.org');
console.log(addresses);  // [ '2606:2800:220:1:248:1893:25c8:1946' ]

// Tries the OS API first, falls back to Node.js's own dns.promises.resolve6.
await osDns.withNodeFallback.promises.resolve6('example.org');
```
npm package: @hackoregon/civic-housing
Description: Civic/Housing 2017
Latest version: 0.1.8

# Hack Oregon Housing Project 2016-2017 Season


![Build Status](https://travis-ci.org/hackoregon/housing-frontend.svg?branch=master)

This is a clone of the [Hack Oregon Starter kit](https://github.com/hackoregon/hackoregon-frontend-starter).

#### Guide
1. Get [Node 6.5 +](https://nodejs.org) - I recommend using [Node Version Manager](https://github.com/creationix/nvm#install-script):
2. `git clone https://github.com/hackoregon/team-budget-frontend.git`.
3. `nvm install 6.9.5` and `nvm use` (sets your node version)
4. install [yarn](https://yarnpkg.com/en/docs/install) (using yarn instead of npm for installing dependencies will help keep versions in sync more easily), and run `yarn` from inside the repo to install dependencies.
5. `npm start` - start dev mode (watching tests + linter)
6. `npm test` - run tests
7. `npm run coverage` - run tests w/ coverage

**Note:** When developing, go to [http://localhost:3000/collection/housing](http://localhost:3000/collection/housing) in order to see the project's index route.

#### Using the [Component Library](https://github.com/hackoregon/component-library) in your project
The component libary has been installed as a dependency from an npm build, make sure the version in package.json matches the latest version in the component library repo to have access to all the latest components.
(https://www.npmjs.com/package/@hackoregon/component-library)

To use a component in your project, import the precompiled component from the lib folder

Example:  importing the StoryCard component from the component library

```javascript
import StoryCard from '@hackoregon/component-library/lib/StoryCard/StoryCard';
```

#### Publishing to NPM
The project uses semver and will be published on NPM for consumption in civic-platform. Run the following commands sequentially:
```bash
  $ npm run bump # will provide you a prompt for version bumps & automatic git tagging + tag README with current version
  $ npm publish  # will publish to npm
```
npm package: @hackoregon/emergency-response
Description: Hack Oregon Emergency Response Front-end
Author: David Daniel
Latest version: 0.1.0

## Hack OR Front-End Starter

This is a starter kit for Hack Oregon front-end development using React + Redux.
This repo should help get started and keep the different projects aligned.

#### Guide
1. Get [Node 6.5 +](https://nodejs.org) - I recommend using [Node Version Manager](https://github.com/creationix/nvm).
2. `git clone https://github.com/hackoregon/hackor-frontend-starter.git`.
3. `npm i` - install
4. `npm start` - start dev mode (watching tests + linter)
5. `npm test` - run tests
6. `npm run coverage` - run tests w/ coverage

#### Next up
[ ]  Docs
[ ]  Ability to remove reference files

[![Stories in Ready](https://badge.waffle.io/hackoregon/hackoregon-frontend-starter.png?label=ready&title=Ready)](http://waffle.io/hackoregon/hackoregon-frontend-starter)
npm package: @hackoregon/jinn
Description: Deals with boilerplate for react redux projects
Author: David Daniel
Latest version: 0.2.4

### Jinn
---
###### v 0.2.4

><img src="icon/djinn.png" alt="djinn" style="width:120px">


Jinn is a command line tool to generate react & redux boilerplate.
Thanks to node-plop & plop, this cli boilerplate generator also has prompts via inquirer.

#### Install
```bash
# install globally
$ npm install @hackoregon/jinn -g
# or as a dependency for use with npm scripts
$ npm install @hackoregon/jinn --save-dev
```

#### Docs
```bash
Usage
  $ jinn <cmd> <options>
  $ npm run jinn -- <cmd> <options>

Commands
  -j                            generate .jinnrc file with view and state paths
  -h, --help                    show help menu
  -v, --view <name> <type>      generate <type>[func, class, pure] view template with specified <name>
  -d, --duck <options>          generate duck template with <options>
  --prompt                      generate with prompts
  -version                      get jinn package version

Options
  -p, --package                 option to generate view as it's own package
  --desc                        add description to package via command line
  -a, --all                     option to generate with story, css and connected version
  -r, --reselect                option to generate duck template with reselect
  -s, --story                   option to add story file to view template
  -c, --css                     option to add css modules file to view template
  -x                            option to add connected version of component to view template

Examples
  jinn -v Map -p -s             generate boilerplate for a Map component as a package with storybook file included
  jinn -v Button func -a        generate boilerplate for a Button functional component with all options
  jinn -v Cart class -c         generate boilerplate Cart class component with css modules
  jinn -d App                   generate boilerplate for App duck
```
npm package: @hackoregon/ui-cards
Description: Common library for CIVIC non-map components
Author: jaron@civicsoftwarefoundation.org
Latest version: 0.0.5

# @hackoregon/ui-cards

---

This package contains components related to story cards, which is a modular framework for data visualization storytelling designed to be embeddable.

This package is in alpha, and may have breaking changes.

## Installation

_Latest version:_

```
yarn add @hackoregon/ui-cards@ci
```

## Documentation

Documentation is in [Storybook](https://hackoregon.github.io/civic/)
npm package: @hackoregon/ui-charts
Description: Common library for CIVIC chart components
Author: jaron@civicsoftwarefoundation.org
Latest version: 0.0.5

# @hackoregon/ui-charts

---

This package contains chart and other non-map data visualization components.

This package is in alpha, and may have breaking changes.

## Installation

_Latest version:_

```
yarn add @hackoregon/ui-charts@ci
```

## Documentation

Documentation is in [Storybook](https://hackoregon.github.io/civic/)
npm package: @hackoregon/ui-core
Description: Common library for CIVIC non-map components
Author: jaron@civicsoftwarefoundation.org
Latest version: 0.0.5

# @hackoregon/ui-core

---

This package contains core UI components.

This package is in alpha, and may have breaking changes.

## Installation

_Latest version:_

```
yarn add @hackoregon/ui-core@ci
```

## Documentation

Documentation is in [Storybook](https://hackoregon.github.io/civic/)
npm package: @hackoregon/ui-maps
Description: Common library for CIVIC map components
Author: jaron@civicsoftwarefoundation.org
Latest version: 0.0.5

# @hackoregon/ui-maps

---

This package contains UI mapping and mapping-related components.

This package is in alpha, and may have breaking changes.

## Installation

_Latest version:_

```
yarn add @hackoregon/ui-maps@ci
```

## Documentation

Documentation is in [Storybook](https://hackoregon.github.io/civic/)
npm package: @hackoregon/ui-platform
Description: Common library for CIVIC non-map components
Author: jaron@civicsoftwarefoundation.org
Latest version: 0.0.4

## Hack Oregon's React Component Library

---

Hack Oregon's [React](http://facebook.github.io/react/) Component Library encompasses platform components, a style guide, as well as data visualization components to be shared across projects.

For styling, we are using [Emotion](https://emotion.sh/).

The components that end up here are either built using [React Storybook](https://getstorybook.io) or were ported into the Storybook dev environment. This allows us to make cross project compatibile components. Additionally, this allows us to iterate on design outside the context of a specific project.

Documentation for usage of these components and visual examples will be available on the [Hack Oregon's Storybook](https://hackoregon.github.io/civic/).

# Installation

_Stable version:_

```
yarn add @hackoregon/component-library
```

_Latest version:_

```
yarn add @hackoregon/component-library@ci
```

# Usage

```
// import components individually
import {
  Button,
  BarChart,
  CivicStoryCard,
} from "@hackoregon/component-library";

// global styles
import "@hackoregon/component-library/assets/global.styles.css";
```
npm package: @hackoregon/utils
Description: Common utils for CIVIC
Author: jaron@civicsoftwarefoundation.org
Latest version: 0.0.5

# @hackoregon/utils

---

This package contains useful internal utility functions.

This package is in alpha, and may have breaking changes.

## Installation

_Latest version:_

```
yarn add @hackoregon/utils@ci
```

## Documentation

Documentation is in [Storybook](https://hackoregon.github.io/civic/)
npm package: @hackoregon/webpacker
Description: Compose your webpack configs - comes with a default
Author: David Daniel
Latest version: 0.1.7

### Webpacker
---
###### v 0.1.7

Webpacker comes with a default config and some utilities.

`Webpacker.composeConfig` allows you to add to a config object so you can further modularize your webpack configs.

#### Install
```bash
$ npm install @hackoregon/webpacker --save-dev
```


```javascript
// entry.js
export default {
  entry: 'src/index.js'
}

// plugins.js
import webpack from 'webpack';

export default {
  plugins: [
    new webpack.optimize.UglifyJsPlugin({
      sourceMap: true,
      compress: {
        warnings: false,
      },
    }),
  ]
}

// webpack.config.js
import { composeConfig, defaultConfig } from '@hackoregon/webpacker';
import pluginsConfig from './plugins'
import entryConfig from './entry'

export default composeConfig(
  defaultConfig,
  entryConfig,
  pluginsConfig
);
```
npm package: @hackr/multi-babel
Description: Add this plugin to generate mirrored esm modules for your existing bundles
Author: Prateek Bhatnagar
Latest version: 1.1.0

# @hackr/multi-babel
![Build Status](https://travis-ci.com/athackr/webpack-multi-babel-plugin.svg?branch=master)

Add this plugin to generate an alternative babel compilation for your existing bundles. It's a fork of [`prateekbh/babel-esm-plugin`](https://github.com/prateekbh/babel-esm-plugin)
Works with Webpack4 and Babel7

```
yarn add -D @hackr/multi-babel
```

### Note
This plugin only works when you're already using `babel-preset-env`.

Also, there is an expectation that your `babel-preset-env` is configured in the shape:
```
{
  use: {
    loader: 'babel-loader',
    options: {
      "presets": [["@babel/preset-env", {
        "targets": {
          "browsers": ["last 2 versions", "safari >= 7"]
        }
        ....
      }]]
    },
  },
}
```

## Options
```js
new MultiBabelPlugin({
  filename: 'es6/[name].js',
  chunkFilename: 'es6/[id].js',
  excludedPlugins: [...],
  additionalPlugins: [...],
  beforeStartExecution: function(plugins, babelConfig) {}
});
```
1. `filename`: Output name of es6 bundles. (default: '[name].es6.js')
2. `chunkFilename`: Output name of es6 chunks. (default: '[id].es6.js')
3. `excludedPlugins`: List of plugins you want to exclude from generating es6 bundles.
4. `additionalPlugins`: List of plugins you want to add while generating es6 bundles.
5. `beforeStartExecution`: A callback function which passes all plugins and the new babel config, to a function where the user can modify them before starting the `ESM` build.

## How to use
```js
  const MultiBabelPlugin = require('@hackr/multi-babel');

  module.exports = {
    entry: {
      index: './index.js',
      home: './index2.js'
    },
    output: {
      filename: "[name].js"
    },
    module: {
      rules: [
        {
          test: /\.js$/,
          exclude: /(node_modules|bower_components)/,
          use: {
            loader: 'babel-loader',
            options: {
              "presets": [["@babel/preset-env", {
                "targets": {
                  "browsers": ["last 2 versions", "safari >= 7"]
                }
              }]]
            },
          },
        }
      ]
    },
    plugins: [
      new MultiBabelPlugin()
    ]
  }
```
npm package: @hacksaw/create-lib
Description: A minimal, ESM TypeScript library template
Author: Jacob Stordahl
Latest version: 0.0.4

# @hacksaw/create-lib

Generate minimal, ESM based TypeScript libraries configured with modern tooling

## Features

- [Biome](https://biomejs.dev/) setup to format and lint your code
- Auto-generated docs via TypeDoc
- Github Actions configured to 
  - Run [Vitest](https://vitest.dev/) tests on PR's and pushes to the main branch
  - Publish to [npm](https://npmjs.com) and [jsr](https://jsr.io) with Provenance

## Usage

npm
```shell
npx @hacksaw/create-lib
```
pnpm
```shell
pnpm dlx @hacksaw/create-lib
```
yarn
```shell
yarn dlx @hacksaw/create-lib
```
npm package: @hacksaw/gkv
Description: KV for Google Cloud, backed by Cloud Storage
Author: jacob@hacksaw.software
Latest version: 0.0.4

KV for Google Cloud, backed by Cloud Storage

## Installation
```shell
npm install @hacksaw/gkv
pnpm add @hacksaw/gkv
yarn add @hacksaw/gkv
```

## Usage
```typescript
import { Storage } from '@google-cloud/storage';
import { GKV } from '@hacksaw/gkv';

const bucket = "my-bucket"
const storage = new Storage();

const kv = new GKV<string, string>({ bucket, storage })

await kv.set('my-key', 'some value')

const value = await kv.get("my-key")

console.log(value) // 'some value'
```

> [!NOTE]
> Visit [Github](https://github.com/hacksawsoftware/gkv/tree/main/examples) to see more examples
npm package: @hacksaw/warden
Description: A JavaScript Monorepo Script Runner
Author: Jacob Stordahl
Latest version: 0.0.1-alpha

# Warden

A JavaScript Monorepo Script Runner

![demo gif](https://github.com/user-attachments/assets/03a56281-042a-4baa-ba40-37b636b4082f)

> [!WARNING]
> Warden is in early development and may have rapid breaking changes. Try it out, but don't depend on it (yet)

## Overview

If you've worked in a large JavaScript monorepo, you likely find yourself needing to run scripts from a number of monorepo packages in an adhoc manner. You likely open up many terminal windows or slip your way through a complex pnpm --filter call, assuming you even remember all your package names. Warden's goal is to provide a more interactive way to run these scripts within a single terminal window.

## Install

Warden is made to be installed globally.

```shell
npm install -g @hacksaw/warden
```

## Usage

Call warden inside your monorepo. The CLI will auto detect your workspace type and deduce your packages from there.

```
warden
```

> [!IMPORTANT]
> Currently, supported workspaces are npm, pnpm, and yarn
npm package: @hacksawstudios/nosleep.js
Description: Prevent display sleep and enable wake lock in any Android or iOS web browser
Author: Rich Tibbett
Latest version: 0.9.1

# NoSleep.js

Prevent display sleep and enable wake lock in all Android and iOS web browsers.

Check out the [live demo](https://richtr.github.io/NoSleep.js/example) in any Android or iOS web browser.

## Installation

This library is available on [Bower](http://bower.io/) as **nosleep**.

`bower install nosleep`

This package is published to npm as **nosleep.js** and can be installed with:

`npm install nosleep.js`

Alternatively, you can manually add [NoSleep.js](https://github.com/richtr/NoSleep.js/blob/master/dist/NoSleep.js) to your project (or the [minified version](https://github.com/richtr/NoSleep.js/blob/master/dist/NoSleep.min.js)).

## Build from source

Install all development dependencies with:

`npm install`

To build this library run:

`npm run build`

A new build of [NoSleep.js](https://github.com/richtr/NoSleep.js/blob/master/dist/NoSleep.js) and [NoSleep.min.js](https://github.com/richtr/NoSleep.js/blob/master/dist/NoSleep.min.js) will now be available in the `/dist` directory.

## Usage

Create a new NoSleep object and then enable or disable it when needed.

To create a new NoSleep object:

```javascript
var noSleep = new NoSleep();
```

To enable wake lock:

**NOTE: This function call must be wrapped in a user input event handler e.g. a mouse or touch handler**

```javascript
// Enable wake lock.
// (must be wrapped in a user input event handler e.g. a mouse or touch handler)
document.addEventListener('click', function enableNoSleep() {
  document.removeEventListener('click', enableNoSleep, false);
  noSleep.enable();
}, false);
```

To disable wake lock:

```javascript
// Disable wake lock at some point in the future.
// (does not need to be wrapped in any user input event handler)
noSleep.disable();
```

See [example/index.html](https://github.com/richtr/NoSleep.js/blob/master/example/index.html) (and the [live demo](https://richtr.github.io/NoSleep.js/example)) for more information.

## Feedback

If you find any bugs or issues please report them on the [NoSleep.js Issue Tracker](https://github.com/richtr/NoSleep.js/issues).

If you would like to contribute to this project please consider [forking this repo](https://github.com/richtr/NoSleep.js/fork), making your changes and then creating a new [Pull Request](https://github.com/richtr/NoSleep.js/pulls) back to the main code repository.

## License

MIT. Copyright (c) [Rich Tibbett](https://twitter.com/_richtr).

See the [LICENSE](https://github.com/richtr/NoSleep.js/blob/master/LICENSE) file.
npm package: @hacksc/ui-kit
Description: The official HackSC UI kit
Latest version: 1.0.2

# HackSC official UI kit

We build everything here :)

## Available Scripts

### `npm test`

Launches the test runner in the interactive watch mode.

### `npm run build`

Builds the UI kit for production to the `build` folder. It correctly bundles React in production mode and optimizes the build for the best performance.

The build is minified and the filenames include the hashes.

## Testing the UI kit in a demo app

If you want to test your changes for the UI kit on a separate React app, you
will need to temporarily symlink the React dependency of your demo app to this package.

The reason is because we use React hooks in this UI kit :) and you would be running 2 instances of React per [this](https://legacy.reactjs.org/warnings/invalid-hook-call-warning.html#duplicate-react) when you do `npm link @hacksc/ui-kit` in your demo app if you don't do the below steps (or equivalent steps to ensure only one React instance is present on your demo app).

1. `cd` to your demo app folder (should be a React/Next.js app)
2. Make sure you installed all dependencies in your demo app via your favorite `install` command. This app must have a React dependencies version that is compatible with the React version specified in this package (in `package.json`'s `peerDependencies`)
3. `cd` back to our UI kit folder, and `npm link ${PATH_TO_APP}/node_modules/react` to temporarily symlink the demo app's React to this UI kit.
   the UI kit's 
4. Run `npm link` to create a global symlink for this UI kit
6. `cd` back to the demo app
7. Run `npm link @hacksc/ui-kit` to symlink the global symlink for the UI kit
   into the app's `node_modules`
8. Start the demo app and start playing around with the kit! Since it's a
   symlink, any changes to the UI kit in the `ui-kit/` folder will require a `build` first before it reflects on
   the demo app.