open-index/open-npm huggingface dataset:
npm package: @joe8bit/note-maker
Description: A simple CLI tool to make markdown note taking easier
Author: Joe Pettersson
Latest version: 2.0.0

## Note-maker

> If you are not me, this CLI tool is likely to provide *zero* value

A tool for creating the skeleton of Markdown notes (based on templates) in the current directory and then optionally opening them in `$EDITOR`.

### Usage

```
npm install -g @Joe8Bit/note-maker
(cd into whichever directory you choose)
note-maker
```

The tool will then run you through a short config to populate the template.

Assuming you run through the template, a Markdown file will be generated in the current directory with a filename in the following format `[MMM Do YYYY] - [title from wizrd].md`

Optionally, you can pass the `-e` argument to the `note-maker` command and it will open the written file in your `$EDITOR`.

There are also several environment variables that can be configured to control `note-maker` behaviour:

* `NOTE_TEMPLATE_PATH` which tells the tool where to look for it's template directory, it overrides the default
  * It will try to find templates in that directory, as specified during the wizard in the `[template_name].md.ejs` format
* `NOTE_SAVE_PATH` which overrides the `process.cwd()` call and will always save notes in this directory if it is set
* `NOTE_TEMPLATE_SUFFIX` which overrides the suffix for a template

## Testing

```
npm test
```

Tests will fail if coverage <100%

### License

MIT
npm package: @joe_kerr/electron-context-bridge
Description: Electron context bridge between Main World (renderer) and Preload Isolated World.
Author: Joe Kerr
Latest version: 0.1.1

# Electron plugin for an isolated preload script

Run code in Electron's Main World (renderer) that is isolated, as much as possible, from the Preload Isolated World. This is achieved by using a context bridge. An Electron [context bridge](https://www.electronjs.org/docs/api/context-bridge) is required for **security purposes**.

The current version has some open points on the todo list. Interfaces may change.


# Install

```
npm install @joe_kerr/electron-context-bridge
```


# Usage

```javascript
const {ContextBridgeMain} = require("@joe_kerr/electron-context-bridge");
const contextBridge = new ContextBridgeMain(BrowserWindow);
```

```javascript
//  (...)
const win = new BrowserWindow({
   webPreferences: {
    preload: contextBridge.getPreloadFilePath(),
    nodeIntegration: false,			
    contextIsolation: true //*required!
  }
});
```

Two types of communication are implemented:

- Renderer-Main request-response model
- Main broadcast


**Request-response**

```javascript
//Main: Setup message channel
contextBridge.createIpcChannel("getPrinters", async (filterList)=>{
  const printers = browserWindow.webContents.getPrinters();	
  return filter(printers, filterList);
});	
```

```javascript
//Renderer: send request to main and get response
async function doSth() {
  const result = await window.$electron.request("getPrinters", optionalEgAFilterList);
}
```


**Broadcast**

```javascript
//Renderer: listen for message event
window.$electron.on("broadcast-event", function(event) {
  console.log(event.detail); //"broadcast-message"
  document.getElementById("response").textContent = event.detail;
});
```

```javascript
//Main: send message event
contextBridge.broadcastMessage("broadcast-event", {data: "broadcast-message"});
```


# Versions

## 0.1.1
- Fix: Removed full exposure of ipcRenderer in Preload

## 0.1.0
- Chg: Code cleanup and refactoring

**Breaking changes**

- Chg: Removed todo code for parameter validation. Requirements too diverse, user responsibility

## 0.0.1
- Public beta release.


# Copyright

MIT (c) Joe Kerr since 2020
npm package: @joe_kerr/stackthemmodals
Description: Stack them modals.
Author: joe_kerr / Joe-Kerr
Latest version: 1.0.7

# StackThemModals: modal stack controller

Modal elemets are all around the place, be it popups, tooltips, context menus, widgets like colour pickers, and so on. So technically, for every element you needed to set up a document click listener, check whether clicks went inside or outside the element, evaluate what to do if there are modal elements on top of modal elements, etc.

Since this is far from being just a one-liner, it makes sense to provide this as a separate service.


## Features
- Only one listener for all modal elements.
- Knows what modals to close if multiples are opened.


## Demo

[See it in action.](https://joe-kerr.github.io/stackThemModals/)


## Requirements

- Web browser


## Install

**1)**
```
npm install @joe_kerr/stackthemmodals
```

**2)**

```
import modalStack from "./where_you_put_it/src/index.js";
```

or

```
const modalStack  = require("./where_you_put_it/dist/stackThemModals.common.js");
```

or

```
<html> <script src=""./where_you_put_it/dist/stackThemModals.browser.js""></script>
```


## Use

### push(`<dom node>` element, `<func>` callback, config)

Adds modal behaviour to the given element. Calls the callback if clicked outside of the element.

By default, when there are multiple modal elements, clicking outside of element A but within element B only destroys modal behaviour for A.

#### `<obj>`config

- `<bool>`stopPropagation: Should the modal click listener consume the event.

### forcePop(`<bool>`stack)

Cancels the modal behaviour - before it was clicked outside - of the last element (default) or, if the parameter is true, empties the entire stack.

Notice, just to be clear, you only need to call forcePop if you do not want to wait for the user to click outside of the modal. E.g.: if a user selects an option in a select box which should close the underlying modal container.


## Notes
- More options #todo.


## Versions

### 1.0.7
- Fixed: Added missing tests for propagation handling

### 1.0.6
- Changed: Mouse event passed to user callbacks

### 1.0.5
- Changed: Added check in .push if element parameter is DOM el

### 1.0.4
- Fixed: Reversed propagation (issue #1)
- Changed: Simplified live demo

### 1.0.3
- Changed: Added live demo with github pages

### 1.0.2
- Fixed: ohh, I see now: https://github.com/webpack/webpack/issues/7646

### 1.0.1 
- Public release


## Copyright

MIT (c) Joe Kerr 2019
npm package: @joe_six/duarte-watanabe-peak-detection
Description: Detect peaks in data based on their amplitude and other features (ported from python)
Author: dirk lüsebrink
Latest version: 0.2.0

# Detection of peaks in data

Javascript port of an original python function for the detection of peaks in
value arrays. For an understanding of parameters and what this package really
does please checkt this orginal documentation at: 

 - https://nbviewer.jupyter.org/github/demotu/BMC/blob/master/notebooks/DetectPeaks.ipynb

I use it find peaks in my IMS data (more on this another time):

![vosc.png -- IMAGES ARE BROKEN ON NPMJS! :( See github repo for full display..](vosc.png)

## Install 

  $ npm install "@joe_six/duarte-watanabe-peak-detection"

## Usage

```javascript
const detect_peaks = require("@joe_six/duarte-watanabe-peak-detection")

let x = [0, 1, 0, 2, 0, 3, 0, 2, 0, 1, 0]
// set minimum peak distance = 2
var peaks = detect_peaks(x, {mpd: 2})
```

## Notice

The implementation can be found in github: 

 - https://github.com/flowerpilot/Duarte-Watanabe-Peak-Detection-Javascript-Port

This is a 0.1.something release. NOT Optimized, briefly tested, and full of debug code artifacts. But it seems to be working already, for me at least. ymmv, 

have fun
npm package: @joe_six/multi-env-cmd
Description: running scripts in ad-hoc blended enviroments
Author: dirk lüsebrink
Latest version: 0.0.3

# Ad-hoc mixing of multiple .env files into an Environment to run shell Commands in

No a big thing, just mixing up multiple .env config files into an ad-hoc enviroment to run your application in. Usually in development, not production. 

This for example makes up an env on the fly combined from three files:

```sh
$ multi-env .env.sqs.dev .env.db.local .env.saas.staging -- ./bin/app-under-development
```

Like when you have a programm which connects with two different databases, an AWS SQS queue and a external SaaS API. To run this script in dev mode you need to configure all of them, but depending on what you actually work on, you need a different set-up. In this case this are three envs combined, and possibilities multiply. Add test, staging and production and combinations go up beyond what you can handle in a single .env file. 

Add as many .env files you like, end that list with `--` and have your regular cmdline following right after it. The above example results in constructing and executing this shell command: 

```sh
$ (set -a; source .env.sqs.dev && source .env.db.local && source .env.saas.staging && ./bin/app-under-development)
```

Frameworks like laravel support a .env file directly, and in testing even overload it automatically from .env.testing. This script is for such needs, but in a generic way. Packages like [.dotenv](https://www.npmjs.com/package/dotenv) do similar things, but for from inside a node.js app itself. This here is for the cmdline. 

All of this is guided by the idea of [12 Factors](https://12factor.net/config), go read it, if you haven't. Seriously. 

have fun
npm package: @joe_six/pathfix
Description: managing shell PATH variable
Author: dirk lüsebrink
Latest version: 1.0.0

# pathfix.js -- Managing shell's PATH variable

Not such a big, but that is something I needed back in the day when managing various different software packages and switching from one setup to the other tended to allways adding another directory to the shell PATH variable. So one day, I sat down and wrote a little ruby script to remove duplicates from the shell PATH var, append or prepend new directories easily, or, remove dir entries based on regualar expression matching.

```sh
# echo dublicate cleaned PATH variable
$ pathfix

# prepend (from the front) dir to PATH
$ pathfix + /some/local/path

# append dir to PATH
$ pathfix $ /some/local/path

# remove all dirs from path which contain 'ruby'
$ pathfix - ruby
```

But! Tricky! A program CAN'T manuipulate the env var settings of its parent process. Means, the `pathfix` script, cannot CHANGE the PATH var in the surrounding shell. But this is what you usually want. In order to put this script to use, you need to add a little shell function to your env, like this: 

```sh
function path {
    new_path="$(pathfix $*)"
    if [ "$?" -eq 0 ]; then 
        PATH=${new_path}
        export PATH
    fi
}
```

This makes a `path` command available in your shell, and puts whatever the result is from the pathfix script into the PATH variable. Like this:

```sh
$ echo $PATH
/Users/crux/.nvm/versions/node/v16.13.0/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Library/Apple/usr/bin
$ path + ~/bin   
$ echo $PATH
/Users/crux/bin:/Users/crux/.nvm/versions/node/v16.13.0/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Library/Apple/usr/bin
$ 
```
npm package: @joe_six/smoothed-z-score-peak-signal-detection
Description: javascript implementation of the z-score algorithm according to this: https://stackoverflow.com/questions/22583391/peak-signal-detection-in-realtime-timeseries-data/22640362#22640362
Author: dirk lüsebrink
Latest version: 0.1.2

# Peak signal detection in realtime timeseries data

This is just a javascript transcription of the algorithm pseudocode given in the
referenced article put in node npm package:

 - https://stackoverflow.com/questions/22583391/peak-signal-detection-in-realtime-timeseries-data

Please refer to the above URL for documentation of functionallity and proper parameterization.

Included with this module is a command line example and a sample data file
(date from the above URL) to show it working:

  $ smoothed-z-score-demo

or:

  $ smoothed-z-score-demo test-data.csv

Also available as npm package:

 $ npm i @joe_six/smoothed-z-score-peak-signal-detection

have fun


ps.: for the data I actually had I could not really use it.. ;(
npm package: @joealden/graphql-yoga
Description: <p align="center"><img src="https://imgur.com/Sv6j0B6.png" width="100" /></p>
Author: Johannes Schickling
Latest version: 1.16.9

<p align="center"><img src="https://imgur.com/Sv6j0B6.png" width="100" /></p>

# graphql-yoga

graphql-yoga modifed to expose webSocket instance in Subscription resolvers.

https://github.com/prismagraphql/graphql-yoga/issues/424
npm package: @joearasin/redux-form
Description: A higher order component decorator for forms using Redux and React
Author: Erik Rasmussen
Latest version: 3.0.12-a

# redux-form
---
[<img src="http://npm.packagequality.com/badge/redux-form.png" align="right"/>](http://packagequality.com/#?package=redux-form)

[![NPM Version](https://img.shields.io/npm/v/redux-form.svg?style=flat)](https://www.npmjs.com/package/redux-form) 
[![NPM Downloads](https://img.shields.io/npm/dm/redux-form.svg?style=flat)](https://www.npmjs.com/package/redux-form)
[![Build Status](https://img.shields.io/travis/erikras/redux-form/master.svg?style=flat)](https://travis-ci.org/erikras/redux-form)
[![devDependency Status](https://david-dm.org/erikras/redux-form/dev-status.svg)](https://david-dm.org/erikras/redux-form#info=devDependencies)
[![redux-form channel on discord](https://img.shields.io/badge/discord-redux--form%40reactiflux-blue.svg)](https://discordapp.com/channels/102860784329052160/105736485537374208)
[![PayPal donate button](http://img.shields.io/paypal/donate.png?color=yellowgreen)](https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=3QQPTMLGV6GU2)
[![Twitter URL](https://img.shields.io/twitter/url/https/github.com/erikras/redux-form.svg?style=social)](https://twitter.com/intent/tweet?text=With%20@ReduxForm,%20I%20can%20keep%20all%20my%20form%20state%20in%20Redux!%20Thanks,%20@erikras!)

`redux-form` works with [React Redux](https://github.com/rackt/react-redux) to enable an html form in
[React](https://github.com/facebook/react) to use [Redux](https://github.com/rackt/redux) to store all of its state.

[<img src="logo.png" align="right" class="logo" height="151" width="250"/>](http://erikras.github.io/redux-form/)

## Installation
```npm install --save redux-form```

## Documentation

* [Getting Started](http://erikras.github.io/redux-form/#/getting-started)
* [Examples](http://erikras.github.io/redux-form/#/examples)
* [API](http://erikras.github.io/redux-form/#/api)
* [FAQ](http://erikras.github.io/redux-form/#/faq)
* [Release Notes](https://github.com/erikras/redux-form/releases)
* [Tools](https://github.com/erikras/redux-form/blob/master/tools.md)
* [`v2.x.x` documentation](https://github.com/erikras/redux-form/tree/v2.4.5)
npm package: @joeattardi/emoji-button
Description: Vanilla JavaScript emoji picker
Author: Joe Attardi
Latest version: 4.6.4
Deprecated: Emoji Button is now PicMo! Please install the 'picmo' package, see https://picmojs.com for details

![Emoji Button](https://user-images.githubusercontent.com/219285/88242435-2864b400-cc5b-11ea-9b77-b4574ad45f4c.png)


Vanilla JavaScript emoji picker 😎

## Screenshot

![Screenshot](https://user-images.githubusercontent.com/219285/88242157-690ffd80-cc5a-11ea-8b40-fc148d1f7eb7.png)


## Demo and Documentation

[https://emoji-button.js.org](https://emoji-button.js.org)

## Features

* 💻 Vanilla JS, use with any framework
* 😀 Use native or Twemoji emojis
* 🔎 Emoji search
* 👍🏼 Skin tone variations
* ⏱ Recently used emojis
* ⌨️ Fully keyboard accessible
* 🎨 Dark, light, and auto themes
* ⚙️ Add your own custom emoji images
* 🧩 Extend functionality with plugins

## Browser support

Emoji Button is supported on all modern browsers supporting the latest JavaScript features. Internet Explorer is not supported.

## Installation

If you are using a package manager like `yarn` or `npm`, you can install Emoji Button directly from the npm registry:

    npm install @joeattardi/emoji-button

## Basic usage

First, you'll need a trigger element. This is typically a button, and is used to toggle the emoji picker.

```html
<button id="emoji-trigger">Emoji</button>
```

Once you've added the trigger, you will need to import the `EmojiButton` class and create a new instance. Various options can be passed to the constructor, which is covered in the [API documentation](https://emoji-button.js.org/docs/api). 

After constructing a picker, it can be shown by calling `showPicker` or `togglePicker` on it. These functions expect a reference element as a parameter. The picker is positioned relative to this reference element.

When an emoji is selected, the picker will emit an `emoji` event, passing an object containing data about the emoji that was selected. You can then handle the selected emoji however you want.

For more in depth documentation and examples, please visit [https://emoji-button.js.org](https://emoji-button.js.org).

```javascript
import { EmojiButton } from '@joeattardi/emoji-button';

const picker = new EmojiButton();
const trigger = document.querySelector('#emoji-trigger');

picker.on('emoji', selection => {
  // handle the selected emoji here
  console.log(selection.emoji);
});

trigger.addEventListener('click', () => picker.togglePicker(trigger));
```

## Development

The easiest way to hack on Emoji Button is to use the documentation site. First, you should fork this repository.

### Clone the forked repository

    git clone https://github.com/your-name/emoji-button.git

### From the repository root

#### Install dependencies

    npm install

#### Set up the link

    npm link

#### Start the build/watch loop

    npm run build:watch

### From the `site` subdirectory

#### Install dependencies

    npm install

#### Link the library

    npm link @joeattardi/emoji-button

#### Start the documentation site

    npm run develop

### Open the page

http://localhost:8000
npm package: @joeattardi/react-mapquest-static-map
Description: React component for MapQuest static maps
Author: Joe Attardi
Latest version: 1.0.1
Deprecated: This package is no longer supported

# React MapQuest Static Maps

Add MapQuest static maps to your React app

*Note*: This is an unofficial library and is not affiliated with MapQuest in any way.

## [Documentation](https://joeattardi.github.io/react-mapquest-static-map)
 - [API reference](https://joeattardi.github.io/react-mapquest-static-map/api/Map)
 - [Examples](https://joeattardi.github.io/react-mapquest-static-map/examples/MapWithCenter)

## Getting Started

First, you'll need a MapQuest API key. To sign up for an API key, go to [https://developer.mapquest.com](https://developer.mapquest.com).

### Install the package

    npm install --save @joeattardi/react-mapquest-static-map

### Build a map

```javascript
import React from 'react';
import { Map } from '@joeattardi/react-mapquest-static-map';

import { MAPQUEST_API_KEY } from '../config';

export default function BaseExample() {
  return (
    <div>
      <Map apiKey={MAPQUEST_API_KEY} center="Boston, MA" />
    </div>
  );
}
```