open-index/open-npm huggingface dataset:
npm package: @ryancole/scenic
Description: A simple router for react.
Latest version: 0.0.6
Deprecated: this is not intended for use

Two simple concepts: `<Scene>` and `<View>`

```
npm install @ryancole/scenic
```

# Scene

`Scene` places `history` on to `context`. You must provide `Scene` with
`history` via props. On the server, you would likely provide `history` created
via `createMemoryHistory`. On the client, you would likely provide `history`
created via `createBrowserHistory`.

# View

`View` compares the current location `pathname` with its own `path` prop. If any
of the `path` prop values match the current location `pathname`, then the
children of `View` will be rendered. The `path` prop may be a `string` or an
array of `string`.

Alternatively, specifying a `not` prop will cause `View` to render only if the
current location `pathname` does *not* match any of the values of the `path`
prop.

If a value in the `path` prop begins with `/`, matching with pathname will begin
at the beginning of pathname. If the value of the `path` prop does not begin
with `/`, matching with pathname will begin at the end of pathname.

# Link

`Link` is a convenience component for pushing to `history` location.

`Link` supports a custom class name when the current location's pathname matches
the `Link`'s own `to` property value. If the `Link` directs to the current
active location pathname, it will use the `activeClassName` property.

# Example

```js
// in the browser
import createHistory from "history/createBrowserHistory";

// in the server
import createHistory from "history/createMemoryHistory";

// instanciate history
const history = createHistory();

function Application() {
  return (
    <Scene history={history}>

      // utility Link component.
      <Link to="/" activeClassName="active">
        Home
      </Link>

      // straight forward, single path match. matching will begin at the
      // *beginning* of the location pathname.
      <View path="/team">
        <Teams />
      </View>

      // straight forward, single path match with parameters. children
      // will receive `id` as a prop.
      <View path="/team/:id">
        <Team />
      </View>

      // single path match. matching will begin at the *end* of the
      // location pathname.
      <View path="create">
        <CreateTeam />
      </View>

      // single path match that will only render while the current
      // location pathname does not match `/foo`.
      <View not path="/foo">
        <h1>Bar is best</h1>
      </View>

      // multiple path match that will only render while the current
      // location pathname matches any of the provided `path` values.
      <View path={["/foo", "/bar"]}>
        <h1>Bar is best, but Foo is welcome</h1>
      </View>

      // multiple path match that will only render while the current
      // location pathname does *not* match any of the provided `path`
      // values.
      <View not path={["/foo", "/bar"]}>
        <h1>404</h1>
      </View>

    </Scene>
  );
}
```
npm package: @ryancui-/themis
Description: 一些可能有点用的 Utils 工具函数和一些可能有点用的 Vue 3 Composables.
Latest version: 1.0.2

# Themis

一些可能有点用的 Utils 工具函数和一些可能有点用的 Vue 3 Composables.  

```ts
npm install @ryancui-/themis
```
npm package: @ryancwalsh/linting
Description: My TypeScript and Prettier linting rules to keep all of my projects consistent.
Latest version: 1.1.0

# @ryancwalsh/linting

My TypeScript and Prettier linting rules to keep all of my projects consistent.

## Get started

```bash
yarn add -D @ryancwalsh/linting eslint@9.17.0 prettier@3.3.3 --exact
```

Carefully consider running:

```bash
cp node_modules/@ryancwalsh/linting/src/examples/eslint.config.js .
cp node_modules/@ryancwalsh/linting/src/examples/prettier.config.js .
cp -R node_modules/@ryancwalsh/linting/.vscode/ .
```

## Publishing

```bash
npm publish --access=public
```

## TODO

Include rules from 'next/core-web-vitals' and/or 'eslint-config-next'. "eslint-plugin-storybook": "0.12.0", "prettier-plugin-prisma": "5.0.0",

TODO: Solve Could not find a declaration file for module '@ryancwalsh/linting'. '/home/rcwalsh/code/partner_portal/node_modules/@ryancwalsh/linting/src/index.js' implicitly has an 'any' type.
Try `npm i --save-dev @types/ryancwalsh__linting` if it exists or add a new declaration (.d.ts) file containing `declare module '@ryancwalsh/linting';`ts(7016)

Document how to use this repo directly while developing it (how to use the local package via symlink instead of the published one).

# Helpful

https://github.com/gajus/eslint-config-canonical/blob/main/COMPARISON_TABLE.md
https://github.com/gajus/eslint-config-canonical/tags
npm package: @ryandavie/components
Description: This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 7.2.0.
Author: Ryan Davie
Latest version: 0.0.1

# Components

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

## Code scaffolding

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

## Build

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

## Publishing

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

## Running unit tests

Run `ng test components` 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: @ryands17/ddb-cache
Description: A full serverless cache for DynamoDB that uses [ElectroDB](https://electrodb.dev/en/core-concepts/introduction/) under the hood for querying and TTL management.
Latest version: 1.0.1

# DynamoDB as cache

A full serverless cache for DynamoDB that uses [ElectroDB](https://electrodb.dev/en/core-concepts/introduction/) under the hood for querying and TTL management.

## Prerequisites

- PNPM
- Docker (to run tests)

This library also requires a DynamoDB table to be created with the following required fields:

- `pk`: String (HASH key)
- `sk`: String (SORT key)
- `ttl`: Number (DynamoDB TTL field)

## Scripts

- `pnpm test`: Run all tests
- `pnpm build`: Build the lib for CJS and ESM

## Usage

Setup a DynamoDB table with the above fields (`pk`, `sk` and `ttl`). Then create an instance of the cache as follows:

```ts
const client = new DynamoDBClient();
// pass in the client, table name, namespace (optional) and TTL in seconds (optional)
const cache = new DynamoDBCache(client, 'cache-table-name', 'my-app-name', 60);
```

To set an item on the cache, use:

```ts
await cache.set('keyName', 'value');
```

To fetch an item, use:

```ts
const value = await cache.get('keyName');
```

The other methods are:

```ts
await cache.delete('keyName');

const isKeyPreset: boolean = await cache.has('keyName');

// clear all values from a namespace
await cache.clear('my-app-name');
```