open-index/open-npm huggingface dataset:
npm package: @kenan/renovate-config
Description: Renovate config for KenanY projects
Author: Kenan Yildirim
Latest version: 1.5.1

# @kenan/renovate-config

Renovate config for KenanY projects.

## Installation

```bash
$ npm install @kenan/renovate-config
```

## Usage

Within renovate's configuration file:

```json
{
  "extends": ["@kenan"]
}
```
npm package: @kenc-ui/angular
Description: Angular components for Clarity
Author: clarity
Latest version: 0.0.1

### Installing Clarity Angular

1.  Install Clarity Icons package through npm:

    ```
    npm install @clr/icons
    ```

2.  Install Clarity UI package through npm:

    ```
    npm install @clr/ui
    ```

3.  Install the clarity-angular package through npm:

    ```
    npm install @clr/angular
    ```

4.  Import the ClarityModule into your Angular application's module. Your application's main module might look like this:

    ```
    import { NgModule } from '@angular/core';
    import { BrowserModule } from '@angular/platform-browser';
    import { ClarityModule } from '@clr/angular';
    import { AppComponent } from './app.component';

    @NgModule({
        imports: [
            BrowserModule,
            ClarityModule,
            ....
         ],
         declarations: [ AppComponent ],
         bootstrap: [ AppComponent ]
    })
    export class AppModule {    }
    ```
npm package: @kenc-ui/icons
Description: Custom Element Icons for Clarity
Author: clarity
Latest version: 0.0.1

### Installing Clarity Icons

1.  Install Clarity Icons package through npm:

    ```
    npm install clr-icons
    ```

2.  Install the polyfill for Custom Elements:

    ```
    npm install @webcomponents/custom-elements
    ```

3.  Include the clr-icons.min.css and clr-icons.min.js in your HTML. As clr-icons.min.js is dependent on the Custom Elements polyfill, make sure to include it before clr-icons.min.js:

    ```
    <link rel="stylesheet" href="path/to/node_modules/clr-icons/clr-icons.min.css">

    <script src="path/to/node_modules/@webcomponents/custom-elements/custom-elements.min.js"></script>
    <script src="path/to/node_modules/clr-icons/clr-icons.min.js"></script>
    ```
npm package: @kenc-ui/ui
Description: CSS for kenc
Author: clarity
Latest version: 0.0.1

### Installing Clarity UI

1.  Install Clarity UI package through npm:

    ```
    npm install @clr/ui
    ```

2.  Install Clarity Icons package through npm:

    ```
    npm install @clr/icons
    ```

3.  Include the clr-ui.min.css and clr-icons.min.css files in your HTML file:

    ```
    <link rel="stylesheet" href="path/to/node_modules/@clr/ui/clr-ui.min.css">
    <link rel="stylesheet" href="path/to/node_modules/@clr/icons/clr-icons.min.css">
    ```

4.  Include the clr-icons.min.js in your HTML file:

    ```
    <script src="path/to/node_modules/clr-icons/clr-icons.min.js"></script>
    ```

5.  Write your HTML with the Clarity CSS class names and markup.
npm package: @kenchan0130/markdown-to-atlassian-wiki-markup-cli
Description: Command line interface of markdown-to-atlassian-wiki-markup (https://github.com/kenchan0130/markdown-to-atlassian-wiki-markup)
Author: Tadayuki Onishi
Latest version: 0.7.0

# @kenchan0130/markdown-to-atlassian-wiki-markup-cli

[![NPM version][npm-image]][npm-url]
[![Build status][github-actions-image]][github-actions-url]
[![dep][dep-image]][dev-dep-url]
[![dev dep][dev-dep-image]][dev-dep-url]
[![snyk][snyk-image]][snyk-url]
[![MIT][mit-image]][mit-url]

[npm-image]: https://img.shields.io/npm/v/@kenchan0130/markdown-to-atlassian-wiki-markup-cli.svg
[npm-url]: https://www.npmjs.com/package/@kenchan0130/markdown-to-atlassian-wiki-markup-cli

[github-actions-image]: https://github.com/kenchan0130/markdown-to-atlassian-wiki-markup-cli/workflows/CI/badge.svg
[github-actions-url]: https://github.com/kenchan0130/markdown-to-atlassian-wiki-markup-cli/actions?query=workflow%3A%22CI%22

[dep-image]: https://badgen.net/david/dep/kenchan0130/markdown-to-atlassian-wiki-markup-cli?label=deps
[dep-url]: https://david-dm.org/kenchan0130/markdown-to-atlassian-wiki-markup-cli

[dev-dep-image]: https://badgen.net/david/dep/kenchan0130/markdown-to-atlassian-wiki-markup-cli?label=devDeps
[dev-dep-url]: https://david-dm.org/kenchan0130/markdown-to-atlassian-wiki-markup-cli?type=dev

[snyk-image]: https://snyk.io/test/npm/@kenchan0130/markdown-to-atlassian-wiki-markup-cli/badge.svg
[snyk-url]: https://snyk.io/test/npm/@kenchan0130/markdown-to-atlassian-wiki-markup-cli

[mit-image]: https://badgen.net/npm/license/@kenchan0130/markdown-to-atlassian-wiki-markup-cli
[mit-url]: https://github.com/kenchan0130/markdown-to-atlassian-wiki-markup-cli/blob/master/LICENSE

Command line interface of [markdown-to-atlassian-wiki-markup](https://github.com/kenchan0130/markdown-to-atlassian-wiki-markup)

## Installation

```sh
npm install -g @kenchan0130/markdown-to-atlassian-wiki-markup-cli
# or
yarn global add @kenchan0130/markdown-to-atlassian-wiki-markup-cli
```

## Usage

### Using file path

```sh
markdownToAtlassianWikiMarkup /path/to/markdown-file
```

### Using pipe

```sh
cat /path/to/markdown-file | markdownToAtlassianWikiMarkup
```

## TODO

- Add unit tests
- Support code block options

## Development

### Test

```sh
npm ci
npm run test
```

### Contributing

1. Fork the project
2. Create a descriptively named feature branch
3. Add your feature
4. Submit a pull request

### Release

```sh
npm version major|minor|patch
```

Run this with local master branch.

## License

MIT
npm package: @kenchi/nexus-plugin-prisma
Description: ``` npm install @kenchi/nexus-plugin-prisma # OR yarn add @kenchi/nexus-plugin-prisma ```
Author: Flavian Desverne
Latest version: 0.40.0

<p align="center">
  <img src="https://i.imgur.com/8qvElTM.png" width="300" align="center" />
  <h1 align="center">@kenchi/nexus-plugin-prisma</h1>
</p>

![trunk](https://github.com/kenchi/nexus-plugin-prisma/workflows/trunk/badge.svg)

**Note:** A [replacement](https://github.com/prisma/nexus-prisma/) for this library is under development and available in early preview. More details in [#1039](https://github.com/graphql-nexus/nexus-plugin-prisma/issues/1039). Since the Prisma team is no longer keeping this library up to date with new Prisma versions, we have forked it.

This plugin integrates [Prisma](https://www.prisma.io/) into [Nexus](https://nexusjs.org/). It gives you an API you to project fields from models defined in your Prisma schema into your GraphQL API. It also gives you an API to build GraphQL root fields that allow your API clients to query and mutate data.

You can find the [documentation on the Nexus website](https://nexusjs.org/docs/plugins/prisma/overview).

## Installation

```
npm install @kenchi/nexus-plugin-prisma
# OR
yarn add @kenchi/nexus-plugin-prisma
```
npm package: @kendallroth/api-error-map
Description: Simple API error code mapping
Author: Kendall Roth
Latest version: 0.1.0

# API Error Map

![](https://github.com/kendallroth/api-error-map/workflows/Jest%20Test/badge.svg)

Simple API error code mapping

- [`createErrorUtils`](#createErrorUtils)

## Features

- Map a readable error message from an error
- Check whether an error has a particular code

## `createErrorUtils`

### Usage

The `createErrorUtils` helper creates a set of helpers to work with API error/codes, given a corresponding error map from codes to strings. The error code extractor can be customized to extend the default behaviour.

To use the helpers, create an mapping between API error codes and the corresponding human-readable error messages. Use this mapping to create the error utils, and then export them for use across the application.

> **NOTE:** It is recommended to use short, description error codes; however, this may be out of your control (specified by the API).

```js
// utilities/errors.js

const errorMap = {
  NOT_AUTHORIZED: "You are not authorized",
  EVENT_CREATE__DUPLICATE_NAME: "Event already exists",
  // ...
};

const { getError, hasError } = createErrorUtils(errorMap);

export { getError, hasError };
```

The created helpers can be used in other files to determine whether an API error contains a specific error (`hasError`) or to get a readable error from the response (`getError`) (with optional default).

```js
// Check whether a specific error occurred
const hasThisError = hasError(response.error, "NOT_AUTHORIZED");

// Get a readable error message from an error (or use default if not matched)
const errorMessage = getError(response.error);
// Get a readable error message with customized default (if not matched)
const errorMessageDefault = getError(response.error, "Something went wrong!");
```

### API

#### `createErrorUtils(errorMap, options)`

| Parameter | Type | Default | Description |
|-----------|------|---------|-------------|
| `errorMap` | `Object` | `{}` | Error mapping between codes and messages
| `options` | `Object` | `{}` | Configuration options
| `options.defaultMessage` | `string` | | Default error message if no matching code is found
| `options.getErrorCode(error)` | `function` | _See below_ | Function to extract error code from error

> **NOTE:** The default `getErrorCode` function simply returns the error as a code if it is a string; otherwise, it will check a few common error keys (`code`, `error`) before returning the error message.

## Miscellaneous

> Project boilerplate from: [`flexdinesh/npm-module-boilerplate`](https://github.com/flexdinesh/npm-module-boilerplate)
npm package: @kendelchopp/pdga-api
Description: PDGA Api Connectivity
Author: Kendel Chopp
Latest version: 1.0.0

# @kendelchopp/pdga-api
## Disclaimer
This project has **NO AFFILIATION** with the PDGA.

## Getting Started
### API Permission
You must get permission to use the PDGA API from the PDGA. You must also adhere to their use guidelines. You can find more information on that at https://www.pdga.com/dev.

Once you have permission, you will be able to use this package and all of its functionality.

### Install The Package
```bash
npm install --save @kendelchopp/pdga-api
```

## Guide
For a small demo project see: https://github.com/KendelChopp/pdga-api-demo

**Note**: All examples are working under the assumption you import this package as PdgaApi. For example:

```javascript
const PdgaApi = require('@kendelchopp/pdga-api');
```

### Authentication
To authenticate, you must make a `login` call. You can either call `login` with a username and password, or with a session name and session id. This is an asynchronous call, and you should wait for this call to finish before trying to make further calls.

#### Username/Password
```javascript
PdgaApi.login({
  username: 'My Cool Username',
  password: 'My Fancy Secret Password'
});
```

#### Session Name/ID
This might be wise if you are doing the authentication elsewhere and want to retain the same session name and id. If you use this method, no network requests will be required for the login.

```javascript
PdgaApi.login({
  sessionName: 'some-session-name',
  sessionId: 'some-session-id'
});
```

### Courses
Allows you to read courses. Currently, they only have search functionality.

#### Search
```javascript
const courses = await PdgaApi.Course.search({
  stateProv: 'VA'
});
```

### Events
Allows you to read events/tournaments. Currently, they only have search functionality.

#### Search
```javascript
const tournaments = await PdgaApi.Event.search({
  tier: 'NT,M',
  startDate: '2022-01-01'
});
```

### Players
Allows you to read players and their stats. Currently, they have search functionality and stats.

#### Search
```javascript
const players = await PdgaApi.Player.search({
  pdgaNumber: '180146'
});
```

#### Stats
```javascript
// Get stats for a particular player
const players = await PdgaApi.Player.search({
  pdgaNumber: '180146'
});
const player = players[0];
const stats = await player.getStats();

// Search for a player and get stats
const searchedStats = await PdgaApi.Player.searchStats({
  pdgaNumber: '180146'
});
```
npm package: @kendraio/console
Description: Kendraio Console
Author: Kendraio @kendraio
Latest version: 0.0.2

kendraio-console
================

Kendraio Console

[![oclif](https://img.shields.io/badge/cli-oclif-brightgreen.svg)](https://oclif.io)
[![Version](https://img.shields.io/npm/v/@kendraio/console.svg)](https://npmjs.org/package/@kendraio/console)
[![Downloads/week](https://img.shields.io/npm/dw/@kendraio/console.svg)](https://npmjs.org/package/@kendraio/console)
[![License](https://img.shields.io/npm/l/@kendraio/console.svg)](https://github.com/kendraio/kendraio-console/blob/master/package.json)

<!-- toc -->
* [Usage](#usage)
* [Commands](#commands)
<!-- tocstop -->
# Usage
<!-- usage -->
```sh-session
$ npm install -g @kendraio/console
$ kendraio COMMAND
running command...
$ kendraio (-v|--version|version)
@kendraio/console/0.0.2 linux-x64 node-v10.11.0
$ kendraio --help [COMMAND]
USAGE
  $ kendraio COMMAND
...
```
<!-- usagestop -->
# Commands
<!-- commands -->
* [`kendraio hello [FILE]`](#kendraio-hello-file)
* [`kendraio help [COMMAND]`](#kendraio-help-command)

## `kendraio hello [FILE]`

describe the command here

```
USAGE
  $ kendraio hello [FILE]

OPTIONS
  -f, --force
  -h, --help       show CLI help
  -n, --name=name  name to print

EXAMPLE
  $ kendraio hello
  hello world from ./src/hello.ts!
```

_See code: [src/commands/hello.ts](https://github.com/kendraio/kendraio-console/blob/v0.0.2/src/commands/hello.ts)_

## `kendraio help [COMMAND]`

display help for kendraio

```
USAGE
  $ kendraio help [COMMAND]

ARGUMENTS
  COMMAND  command to show help for

OPTIONS
  --all  see all commands in CLI
```

_See code: [@oclif/plugin-help](https://github.com/oclif/plugin-help/blob/v2.1.2/src/commands/help.ts)_
<!-- commandsstop -->