open-index/open-npm huggingface dataset:
npm package: @purnell/virtual-table
Description: This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 10.1.6.
Author: purnellcreative
Latest version: 1.0.12

# VirtualTable

This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 10.1.6.

## Code scaffolding

Run `ng generate component component-name --project virtual-table` to generate a new component. You can also use `ng generate directive|pipe|service|class|guard|interface|enum|module --project virtual-table`.
> Note: Don't forget to add `--project virtual-table` or else it will be added to the default project in your `angular.json` file. 

## Build

Run `ng build virtual-table` to build the project. The build artifacts will be stored in the `dist/` directory.

## Publishing

After building your library with `ng build virtual-table`, go to the dist folder `cd dist/virtual-table` and run `npm publish`.

## Running unit tests

Run `ng test virtual-table` to execute the unit tests via [Karma](https://karma-runner.github.io).

## Further help

To get more help on the Angular CLI use `ng help` or go check out the [Angular CLI README](https://github.com/angular/angular-cli/blob/master/README.md).
npm package: @purnomo_eko/remove-stop-words
Description: Remove stop words from search query
Author: eko.purnomo@icloud.com
Latest version: 0.0.4

# Remove-stop-words
Remove stop words from search query to improve search query result.

## How to use it?

The stop words stored in array, and it will remove every words that listed in those array:

```
const removeStopWords = require('@purnomo_eko/remove-stop-words');

removeStopWords('I want to have relationship with different religion', 'en');

// result will be [ 'relationship', 'different', 'religion' ]

```

## Available language
Now we only support english, any addition will be welcome.
npm package: @purphoros/gatsby-plugin-svg-sprite-loader
Description: Create SVG sprites using SVG sprite loader
Author: stldo
Latest version: 0.2.0

# gatsby-plugin-svg-sprite-loader

Gatsby plugin for creating SVG sprites using [External SVG Sprite][1].

[1]: https://github.com/bensampaio/external-svg-sprite-loader

## Install

```bash
$ npm install gatsby-plugin-svg-sprite-loader
```

## Configure

```javascript
// gatsby-config.js

module.exports = {
  plugins: [
    {
      resolve: `gatsby-plugin-svg-sprite-loader`,
      options: {
        /* External SVG Sprite loader options */
        pluginOptions: {
          /* External SVG Sprite plugin options */
        }
      },
    },
  ],
}
```

## Options

### options

Default:
`{ name: 'sprites.[contenthash].svg', iconName: '[name]--[hash:base64:5]' }`;
Type: `Object`.

The `options` object is passed directly to __External SVG Sprite__ loader, more
info can be found [here][2]. To keep consistency, `name` and `iconName` default
values use the same formats used by Gatsby.js for CSS files.

[2]: https://github.com/bensampaio/external-svg-sprite-loader#options

### pluginOptions

Default: `{}`; Type: `Object`.

The `pluginOptions` parameter is passed to __External SVG Sprite__ plugin.

## Usage

```javascript
import React from 'react'
import icon from 'images/icon.svg'

export default () => (
  <svg viewBox={icon.viewBox}>
    <use xlinkHref={icon.url}/>
  </svg>
)
```

```css
.icon {
  background-image: url('images/icon.svg') no-repeat 0;
}
```

## Updating from v0.1.* to v0.2.*

While v0.1.* uses __SVG sprite loader__ under the hood, v0.2.* uses
__External SVG Sprite__. The new package returns the sprite url using the
`symbol` property, while __SVG sprite loader__ uses `url`. A patch was created
to return the value inside the `url` property, among with `symbol`. If the
default options were being used in v0.1.*, no difference should be noticed.

## License

[The MIT License](./LICENSE)
npm package: @purphoros/gatsby-source-thirdparty
Description: Gatsby plugin to handle any third party api data intake.
Author: Anthony Bonventre
Latest version: 1.0.5

# gatsby-source-thirdparty

A gatsby source plugin for pulling in third party api data.

## Features

* Pulls data from configured api url
* Uses custom name to allow for multiple instances of plugin
* Option to download the json data to a configurable path
* Option to only download the json data, and skip inserting it into GraphQL
* Supports simple authentication through axios

## Install

`npm install --save gatsby-source-thirdparty`

## How to use

```javascript
// Place configuration options in your gatsby-config.js

plugins: [
  {
    resolve: 'gatsby-source-thirdparty',
    options: {
      // The url, this should be the endpoint you are attempting to pull data from
      url: `http://yourapi.com/api/v1/posts`,

      // Name of the data to be downloaded.  Will show in graphQL or be saved to a file
      // using this name. i.e. posts.json
      name: `posts`,

      // Optional simple authentication
      auth: {
        username: 'myusername',
        password: 'supersecretpassword1234'
      },

      // Optional payload key name if your api returns your payload in a different key
      // Default will use the full response from the http request of the url
      payloadKey: `body`,

      // Optionally save the JSON data to a file locally
      // Default is false
      localSave: true,

      //  Required folder path where the data should be saved if using localSave option
      //  This folder must already exist
      path: `${__dirname}/src/data/auth/`

      // Optionally include some output when building
      // Default is false
      verboseOutput: true, // For debugging purposes

      // Optionally skip creating nodes in graphQL.  Use this if you only want
      // The data to be saved locally
      // Default is false
      skipCreateNode: true, // skip import to graphQL, only use if localSave is all you want
    }
  }
];

```

## How to query

Data will be available at the following points in GraphQL.

`allThirdPartyName` or `thirdPartyName` where `Name` is replaced by the name entered in the
configuration options.

### Conflicting keys

Some of the returned keys may be transformed if they conflict with restricted keys used for
GraphQL such as the following `['id', 'children', 'parent', 'fields', 'internal']`

These conflicting keys will now show up as `thirdParty_id`