open-index/open-npm huggingface dataset:
npm package: @mwanninger/migrate-mongodb-files-to-s3
Description: Tool to migrate from mongodb files to s3
Author: @paivaric
Latest version: 0.0.2

# migrate-mongodb-files-to-s3

how to use:

npm i -g @back4app/migrate-mongodb-files-to-s3

migrate --mongoUri mongodb://user:pass@host:port/db --appId your_appId --bucket your_bucket
npm package: @mware/ngx-tour-core
Description: [![Dependency Status](https://david-dm.org/isaacplmann/ngx-tour-core.svg)](https://david-dm.org/isaacplmann/ngx-tour-core) [![devDependency Status](https://david-dm.org/isaacplmann/ngx-tour-core/dev-status.svg)](https://david-dm.org/isaacplmann/ngx-tour-c
Author: Isaac Mann
Latest version: 3.0.0

# Ngx-Tour Core
[![Dependency Status](https://david-dm.org/isaacplmann/ngx-tour-core.svg)](https://david-dm.org/isaacplmann/ngx-tour-core)
[![devDependency Status](https://david-dm.org/isaacplmann/ngx-tour-core/dev-status.svg)](https://david-dm.org/isaacplmann/ngx-tour-core?type=dev)

Check out the [documentation/demo page](https://isaacplmann.github.io/ngx-tour).

This is a product tour library built with Angular (2+).  It's inspired by [angular-ui-tour](http://benmarch.github.io/angular-ui-tour).
npm package: @mware/ngx-tour-md-menu
Description: [![Dependency Status](https://david-dm.org/isaacplmann/ngx-tour-md-menu.svg)](https://david-dm.org/isaacplmann/ngx-tour-md-menu) [![devDependency Status](https://david-dm.org/isaacplmann/ngx-tour-md-menu/dev-status.svg)](https://david-dm.org/isaacplmann/n
Author: Isaac Mann
Latest version: 3.1.1

# Ngx-Tour Md-Menu
[![Dependency Status](https://david-dm.org/isaacplmann/ngx-tour-md-menu.svg)](https://david-dm.org/isaacplmann/ngx-tour-md-menu)
[![devDependency Status](https://david-dm.org/isaacplmann/ngx-tour-md-menu/dev-status.svg)](https://david-dm.org/isaacplmann/ngx-tour-md-menu?type=dev)

Check out the [documentation/demo page](https://isaacplmann.github.io/ngx-tour).

This is a product tour library built with Angular (2+).  It's inspired by [angular-ui-tour](http://benmarch.github.io/angular-ui-tour).
npm package: @mwarnerdotme/react-remixicon
Description: React component for the RemixIcon icon library
Latest version: 2.0.1

# @mwarnerdotme/react-remixicon

## Usage

```jsx
import {
  RemixIcon,
  riUserSmileFill,
  riUserSmileLine
} from '@mwarnerdotme/react-remixicon'

export default function MyComponent() {
  return (
    <>
      <RemixIcon icon={riUserSmileFill} size="1x" />
      <RemixIcon
        icon={riUserSmileLine}
        size="2x"
        color="#0000ff"
      />
      <RemixIcon
        icon={riUserSmileFill}
        size="lg"
        className='text-green-500'
      />
      <RemixIcon
        icon={riUserSmileFill}
        size="xxs"
        style={{ display: 'absolute' }}
      />
    </>
  );
}
```

First, import the `<RemixIcon />` component from the library. Then import the icon(s) you want to use in your component. Pass an icon into the `icon` prop of `<RemixIcon />` and: voila! You should now see a beautiful, open-source icon in your component.

## Finding Icons

All available icons can be found on the [official Remix Icon website](https://remixicon.com). Once you've found the icon you're looking for, you'll be able to import it from this library using tree shaking.

> Icon imports follow the convention of `riCamelCaseIconNameVariant` (ex: `riUserSmileFill`).

> Icons with numbers will look like `riHome4Fill`.

## Dev Quickstart

### Generating Icon Typescript Files

All of the icon data will end up in the `src/icons` directory in a designated Typescript file when the `yarn icons:generate` command is ran. Be sure to run `yarn` to download the required devDependencies before running the command.

> `yarn dist` will automatically clear the icon files from this folder before generating new icon files and building.

### Building

Before building, ensure that there are Typescript files for all icons in the `src/icons` directory. Follow the previous section to generate those files programatically (there shouldn't be a need to copy SVG path data manually... unless you really want to).
npm package: @mwater/forms
Description: Form controls for mWater
Author: Clayton Grassick
Latest version: 11.2.7

# mWater Forms

Mobile-friendly survey/form components, compiled from a XForms-inspired JSON schema.

## Features

* 12+ Question types
* Conditions & validations
* Full localization of surveys
* Entity references

## Response Lifecycle

See [Response Lifecycle](docs/Response Lifecycle.md)

### Schema versioning

The schema is stored in _schema field of the form and is an integer. 

The package exports `schemaVersion` which is the current (and maximum) version that it compiles.
It also exports `minSchemaVersion` which is the earliest version supported

### Schema versioning checklist

* Change schema 
* Increment schema version in index.coffee
* Add new version to acceptable _schema enum in schema
* Publish with new major number
* Increment version in mwater-form-designer
* npm install new version of mwater-forms in mwater-form-designer
* Publish mwater-form-designer
* npm install new version of mwater-forms in mwater-server
* Push new server
* npm install new version of mwater-forms in mwater-app
* Deploy new app
* npm install new version of mwater-forms in mwater-portal
* npm install new version of mwater-form-designer in mwater-portal
* Deploy new portal
 
## Entity support

Questions can be linked to entities to support a variety of scenarios:

* Form creates an entity of a certain type with properties mapped to questions
* Form creates an entity of a certain type with properties mapped to questions
* Selecting an entity in an entity question pre-fills answers
* Selecting an entity in an entity question causes other answers to be used to update the entity selected
npm package: @mwater/react-library
Description: React component library
Author: mWater
Latest version: 2.2.1

# react-library

To get started, `npm install` and `bower install`

Then run `gulp demo`. (you might need to `npm install gulp-cli -g`)

Open demo.html in demo/ folder.

## React components

There is a new way to build react components!

Includes:

```
ui = require 'react-library/lib/bootstrap'
update = require 'react-library/lib/update'

```

Define update function:

```
  update: => update(@props.value, @props.onChange, arguments)

```

Create ui components:


```
  R ui.FormGroup, key: "styling", label: "Styling",
    R ui.Check, key: "bold", inline: true, value: @props.value.bold, onChange: @update("bold"), "Bold"
    R ui.Check, key: "italic", inline: true, value: @props.value.italic, onChange: @update("italic"), "Italic"
```

Can also be used to update multiple values (properties of value):

```
  @update({ bold: true, italic: false })
```

Can also be used to update deep properties

```
  @update("styling.bold")
```
npm package: @mwater/visualization
Description: Visualization library
Author: mWater
Latest version: 5.7.0

# mwater-visualization

Requires C3, D3, Bootstrap and Font Awesome

Also requires that server has hexgrid functions (src/maps/Hexgrid Functions.sql)

## Expressions

[Expressions](docs/Expressions.md)

## Principles

* In design, things must be valid or null. Design can be incomplete but not invalid
* After any change design is cleaned before being stored
* Stored design is always cleaned before being edited or displayed

## Quick start

Run `npm run watch` to start the demo
npm package: @mwatson/react-notifications
Description: @mwatson/react-notifications
Author: mbwatson
Latest version: 1.1.0-2

# react-notifications

> @mwatson/react-notifications

[![NPM](https://img.shields.io/npm/v/react-notifications.svg)](https://www.npmjs.com/package/react-notifications) [![JavaScript Style Guide](https://img.shields.io/badge/code_style-standard-brightgreen.svg)](https://standardjs.com)


## Documentation & Examples

[https://mbwatson.github.io/react-notifications](https://mbwatson.github.io/react-notifications) has details about the API and several examples. its code lives in the `example` directory.

## Install

```bash
npm install --save @mwatson/react-notifications
```

## Usage

import the `Notifications` component from `@mwatson/react-notifications`...


```jsx
// App.js
import { Notifications } from '@mwatson/react-notifications'
import 'react-notifications/dist/index.css'
```

...and wrap your application in the `Notifications` component, as it provides context to its descendants.

```jsx
<Notifications>
  <App />
</Notifications>
```

use the `useNotifications` hook to interact with the current notifications in your own components down your application tree.


```jsx
import { useNotifications } from 'react-notifications'

// ...

const Example = () => {
  const { addNotification } = useNotifications()
  return (
    <button onClick={
      addNotification({
        type: 'success',
        text: 'It worked!',
      })
    }>
      Click Me!
    </button>
  )
}
```

the `addNotifications` function takes a `message` object, which has the following shape.

```js
{
  type: 'error' | 'info' | 'success' | 'warning',
  text: String,
  autoClose: boolean, // optional. default: true
  onClick: function, // optional. default: null
  onClose: function, // optional. default: null
}
```

## License

MIT © [mbwatson](https://github.com/mbwatson)
npm package: @mwatson/world-network
Description: Render a D3 map of Earth with a graph (nodes and edges, defined by lon/lat coordinates) superimposed in its surface.
Author: mbwatson
Latest version: 1.0.1-1

# world-network

> Render a D3 map of Earth with a superimposed (non-directed) graph on its surface that consists of edges between nodes whose locations are defined by lon/lat coordinates.

## Install

```bash
npm install --save world-network
```

## Usage

### Imports

Along with React, the `WorldNetwork` component needs to be imported alongside D3. 

```jsx
import React from 'react'
import { WorldNetwork } from '@mwatson/world-network'
import '@mwatson/world-network/dist/index.css'
```

The stylesheet that ships with this module can be pulled from `@mwatson/world-network/dist/index.css`, and it will provide basic styling. This module uses CSS modules, so the resulting class names look something like this: `_styles__country__192bf`. The styles can be overridden by selecting DOM elements by partial class names, like `path[class*="_styles__country"]`, which would select all country paths in the resulting SVG.

### Using the WorldNetwork Component

Use the WorldNetwork component within your React component by passing it the following props: `projection`, `scale`, `nodes`, and `edges`, which will be detailed below.

```jsx
<WorldNetwork
  projection="geoOrthographic" 
  scale={ 300 }
  nodes={ nodes }
  edges={ edges }
/>
```

### Props

#### Projection

The projection props takes a string equal to one of the following of D3's built-in projections:

- geoAlbers
- geoAzimuthalEqualArea
- geoAzimuthalEquidistant
- geoConicConformal
- geoConicEqualArea
- geoConicEquidistant
- geoEqualEarth
- geoEquirectangular
- geoGnomonic
- geoMercator
- geoNaturalEarth1
- geoOrthographic
- geoProjection
- geoTransverseMercator

#### Scale

Because the result from different projections can vary the size and shape of the rendered map, the scale prop is exposed to adjust for this.

#### Nodes

The nodes props receives an Array of Objects of the following shape:

```json
{
  "id": "london",
  "name": "London",
  "location": [-0.1275, 51.50722]
}
```
where `id` is a unique identifier for the node, `name` is the name to display to the client, and `location` is an Array of coordinates (Numbers): `[longitude, latitude]`.

#### Edges

The edges prop receives an Array of two-dimensional Arrays, each of which identifies two nodes to be connected by a path in the resulting graph. This edge Array would instruct the WorldNetwork component to draw three (non-directed) edges between New York City and London, Mexico City, and Zanzibar.

```json
[
  ["london", "new-york-city"],
  ["mexico-city", "new-york-city"],
  ["zanzibar", "new-york-city"]
]
```


## License

MIT © [mbwatson](https://github.com/mbwatson)
npm package: @mwazovzky/vue-drag-drop
Description: Fork of a lightweight Vue wrapper J. Cameron McDonald by [cameronhimself@gmail.com]
Author: Mike Wazovzky
Latest version: 0.0.2

> This is a fork for vue-drag-drop library by J. Cameron McDonald by [cameronhimself@gmail.com]
> original library: https://github.com/cameronhimself/vue-drag-drop
npm package: @mwcp/jaeger
Description: midway component for jaeger
Author: waiting
Latest version: 15.0.0

# [@mw-components/jaeger](https://www.npmjs.com/package/@mw-components/jaeger)

Jaeger opentracing client component for midway.js

[![Version](https://img.shields.io/npm/v/@mw-components/jaeger.svg)](https://www.npmjs.com/package/@mw-components/jaeger)
[![License](https://img.shields.io/badge/license-MIT-blue.svg)](https://opensource.org/licenses/MIT)
[![](https://img.shields.io/badge/lang-TypeScript-blue.svg)]()
[![Conventional Commits](https://img.shields.io/badge/Conventional%20Commits-1.0.0-yellow.svg)](https://conventionalcommits.org)


## Install

```sh
npm i @mw-components/jaeger
```

## Usage

Update project `src/configuration.ts`
```ts
import * as jaeger from '@mw-components/jaeger'

@Configuration({
  imports: [
    jaeger,
  ],
  importConfigs: [join(__dirname, 'config')],
})
export class ContainerConfiguration implements ILifeCycle {
}
```

Update project `src/config/config.prod.ts`
```ts
import { TracerConfig } from '@mw-components/jaeger'

export const tracer: TracerConfig = {
  tracingConfig: {
    reporter: {
      agentHost: '127.0.0.1',
    },
  },
}
```

Update project `src/config/config.(local | unittest).ts`
```ts
import { TracerConfig, initLoggingReqHeaders } from '@mw-components/jaeger'

export const tracer: TracerConfig = {
  reqThrottleMsForPriority: 100,
  tracingConfig: {
    reporter: {
      agentHost: '127.0.0.1',
    },
  },
  loggingReqHeaders: [
    ...initLoggingReqHeaders,
    'header-foo',
    'header-bar',
  ],
}
```

## License

[MIT](LICENSE)
npm package: @mwcz/pbp-loading
Description: A bare-bones, square-ish, loading bar.  Web Component.
Latest version: 1.0.2

# pbp-loading

A bare-bones, square-ish, loading bar.  Web Component.

## Attributes

**Only defaults**

```html
<pbp-loading></pbp-loading>
```

**Set the number of boxes in the loading bar**

```html
<pbp-loading box-count=10></pbp-loading>
```

**Set the duration, in seconds, of all the squares pulsing**

```html
<pbp-loading duration=1></pbp-loading>
```

**Start paused, ie: don't automatically start the animation**

_Note: adding this attribute later does not pause the animation, but `.pause()` does._

```html
<pbp-loading paused></pbp-loading>
```

## CSS

```html
<style>
pbp-loading {
  --pbp-loading-box-size: 30px; /* change the box size */
  --pbp-loading-border: 2px dotted rebeccapurple; /* change the border on the boxes */
  --pbp-loading-gap: 0px; /* change the grid-gap between boxes */
  --pbp-loading-grow: 400%; /* how big the boxes grow */
}
</style>
<pbp-loading></pbp-loading>
```

## JS

This element has two methods, `play()` and `pause()`.
npm package: @mwcz/rtw-render
Description: [**📚 Read this template tutorial! 📚**][template-docs]
Latest version: 1.1.0

<div align="center">

  <h1><code>wasm-pack-template</code></h1>

  <strong>A template for kick starting a Rust and WebAssembly project using <a href="https://github.com/rustwasm/wasm-pack">wasm-pack</a>.</strong>

  <p>
    <a href="https://travis-ci.org/rustwasm/wasm-pack-template"><img src="https://img.shields.io/travis/rustwasm/wasm-pack-template.svg?style=flat-square" alt="Build Status" /></a>
  </p>

  <h3>
    <a href="https://rustwasm.github.io/docs/wasm-pack/tutorials/npm-browser-packages/index.html">Tutorial</a>
    <span> | </span>
    <a href="https://discordapp.com/channels/442252698964721669/443151097398296587">Chat</a>
  </h3>

  <sub>Built with 🦀🕸 by <a href="https://rustwasm.github.io/">The Rust and WebAssembly Working Group</a></sub>
</div>

## About

[**📚 Read this template tutorial! 📚**][template-docs]

This template is designed for compiling Rust libraries into WebAssembly and
publishing the resulting package to NPM.

Be sure to check out [other `wasm-pack` tutorials online][tutorials] for other
templates and usages of `wasm-pack`.

[tutorials]: https://rustwasm.github.io/docs/wasm-pack/tutorials/index.html
[template-docs]: https://rustwasm.github.io/docs/wasm-pack/tutorials/npm-browser-packages/index.html

## 🚴 Usage

### 🐑 Use `cargo generate` to Clone this Template

[Learn more about `cargo generate` here.](https://github.com/ashleygwilliams/cargo-generate)

```
cargo generate --git https://github.com/rustwasm/wasm-pack-template.git --name my-project
cd my-project
```

### 🛠️ Build with `wasm-pack build`

```
wasm-pack build
```

### 🔬 Test in Headless Browsers with `wasm-pack test`

```
wasm-pack test --headless --firefox
```

### 🎁 Publish to NPM with `wasm-pack publish`

```
wasm-pack publish
```

## 🔋 Batteries Included

* [`wasm-bindgen`](https://github.com/rustwasm/wasm-bindgen) for communicating
  between WebAssembly and JavaScript.
* [`console_error_panic_hook`](https://github.com/rustwasm/console_error_panic_hook)
  for logging panic messages to the developer console.
* [`wee_alloc`](https://github.com/rustwasm/wee_alloc), an allocator optimized
  for small code size.
npm package: @mweberxyz/undici-types
Description: A stand-alone types package for Undici
Latest version: 6.20.6

# undici-types

This package is a dual-publish of the [undici](https://www.npmjs.com/package/undici) library types. The `undici` package **still contains types**. This package is for users who _only_ need undici types (such as for `@types/node`). It is published alongside every release of `undici`, so you can always use the same version.

- [GitHub nodejs/undici](https://github.com/nodejs/undici)
- [Undici Documentation](https://undici.nodejs.org/#/)
npm package: @mwheelersmith/inputarea
Description: Input Area is a parody module to convert an input with a type of textarea into an actual textarea.
Author: Miles Wheeler-Smith
Latest version: 1.0.4

# Input Area

> Input Area is a parody module to convert an input with a type of textarea into an actual textarea.
> **Please do not use in production!** A textarea is of course the correct control to use.

## Install

```bash
npm install @mwheelersmith/inputarea
```

## Usage

```
inputArea()
```

## License

[MIT](http://vjpr.mit-license.org)
npm package: @mwhitedun/peach-mw
Description: Boilerplate for npm modules with ES6 features and syntax
Latest version: 0.0.12

# NPM Module Boilerplate

[![Build Status](https://travis-ci.org/flexdinesh/npm-module-boilerplate.svg?branch=master)](https://travis-ci.org/flexdinesh/npm-module-boilerplate) [![dependencies Status](https://david-dm.org/flexdinesh/npm-module-boilerplate/status.svg)](https://david-dm.org/flexdinesh/npm-module-boilerplate) [![devDependencies Status](https://david-dm.org/flexdinesh/npm-module-boilerplate/dev-status.svg)](https://david-dm.org/flexdinesh/npm-module-boilerplate?type=dev) [![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](https://opensource.org/licenses/MIT)

**Start developing your NPM module in seconds** ✨

Readymade boilerplate setup with all the best practices to kick start your npm/node module development.

Happy hacking =)

# Features

* **ES6/ESNext** - Write _ES6_ code and _Babel_ will transpile it to ES5 for backwards compatibility
* **Test** - _Mocha_ with _Istanbul_ coverage
* **Lint** - Preconfigured _ESlint_ with _Airbnb_ config
* **CI** - _TravisCI_ configuration setup
* **Minify** - Built code will be minified for performance

# Commands
- `npm run clean` - Remove `lib/` directory
- `npm test` - Run tests with linting and coverage results.
- `npm test:only` - Run tests without linting or coverage.
- `npm test:watch` - You can even re-run tests on file changes!
- `npm test:prod` - Run tests with minified code.
- `npm run test:examples` - Test written examples on pure JS for better understanding module usage.
- `npm run lint` - Run ESlint with airbnb-config
- `npm run cover` - Get coverage report for your code.
- `npm run build` - Babel will transpile ES6 => ES5 and minify the code.
- `npm run prepublish` - Hook for npm. Do all the checks before publishing your module.

# Installation
Just clone this repo and remove `.git` folder.


# License

MIT © Dinesh Pandiyan
npm package: @mwhitedun/plum-mw
Description: Boilerplate for npm modules with ES6 features and syntax
Latest version: 0.0.12

# NPM Module Boilerplate

[![Build Status](https://travis-ci.org/flexdinesh/npm-module-boilerplate.svg?branch=master)](https://travis-ci.org/flexdinesh/npm-module-boilerplate) [![dependencies Status](https://david-dm.org/flexdinesh/npm-module-boilerplate/status.svg)](https://david-dm.org/flexdinesh/npm-module-boilerplate) [![devDependencies Status](https://david-dm.org/flexdinesh/npm-module-boilerplate/dev-status.svg)](https://david-dm.org/flexdinesh/npm-module-boilerplate?type=dev) [![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](https://opensource.org/licenses/MIT)

**Start developing your NPM module in seconds** ✨

Readymade boilerplate setup with all the best practices to kick start your npm/node module development.

Happy hacking =)

# Features

* **ES6/ESNext** - Write _ES6_ code and _Babel_ will transpile it to ES5 for backwards compatibility
* **Test** - _Mocha_ with _Istanbul_ coverage
* **Lint** - Preconfigured _ESlint_ with _Airbnb_ config
* **CI** - _TravisCI_ configuration setup
* **Minify** - Built code will be minified for performance

# Commands
- `npm run clean` - Remove `lib/` directory
- `npm test` - Run tests with linting and coverage results.
- `npm test:only` - Run tests without linting or coverage.
- `npm test:watch` - You can even re-run tests on file changes!
- `npm test:prod` - Run tests with minified code.
- `npm run test:examples` - Test written examples on pure JS for better understanding module usage.
- `npm run lint` - Run ESlint with airbnb-config
- `npm run cover` - Get coverage report for your code.
- `npm run build` - Babel will transpile ES6 => ES5 and minify the code.
- `npm run prepublish` - Hook for npm. Do all the checks before publishing your module.

# Installation
Just clone this repo and remove `.git` folder.


# License

MIT © Dinesh Pandiyan
npm package: @mwillbanks/release-it-expo-bumper-plugin
Description: Release-it plugin for Expo which bumps app.json or app.config.json version numbers.
Author: Mike Willbanks
Latest version: 1.0.0

# Release-It Expo Bumper Plugin

A [release-it](https://github.com/release-it/release-it) plugin that increments the Android version code, iOS build
number, and app version in an [Expo](https://expo.io/) app's `app.json` or `app.config.js` file.

## Installation

```bash
# npm
npm install --save-dev @mwillbanks/release-it-expo-bumper-plugin
# yarn
yarn add --save-dev @mwillbanks/release-it-expo-bumper-plugin
```

## Usage

To use the plugin, add it to the `plugins` array in your `release-it` configuration (`.release-it.json` or
`package.json`):

```
"release-it": {
  "plugins": {
    "@mwillbanks/release-it-expo-bumper-plugin": {}
  }
}
```

Then, run the `release-it bump` task or your general `release-it` task:

```
release-it bump
# or
release-it
```

This will increment the Android version code, iOS build number, and app version in your Expo app's `app.json` or
`app.config.js` file.

## License

MIT
npm package: @mwinel/nasa-image-search
Description: "Nasa image search"
Author: Nelson Murungi
Latest version: 0.1.5

## NASA Image Search

This is a simple web app that allows you to search images by [NASA](https://www.nasa.gov/).

## Demo Link

```
https://nasa-image-search-three.vercel.app/
```

## Getting Started

First, run the development server:

```bash
npm run dev
# or
yarn dev
```

Open [http://localhost:3000](http://localhost:3000) with your browser to see the result.

You can start editing the page by modifying `pages/index.tsx`. The page auto-updates as you edit the file.

[API routes](https://nextjs.org/docs/api-routes/introduction) can be accessed on [http://localhost:3000/api/hello](http://localhost:3000/api/hello). This endpoint can be edited in `pages/api/hello.ts`.

The `pages/api` directory is mapped to `/api/*`. Files in this directory are treated as [API routes](https://nextjs.org/docs/api-routes/introduction) instead of React pages.

## Storybook

The frontend UI components are built (into a Design System), tested, reviewed and packaged in isolation using [Storybook](https://storybook.js.org/).

The design system can be found here [NASA Image Search design system](https://6367f0aed37a0a2c90b92438-vtljkbsxjg.chromatic.com/?path=/story/nasa-image-search-introduction--page).

Run story book:

```bash
npm run storybook
# or
yarn storybook
```