open-index/open-npm huggingface dataset:
npm package: @justinjoram/request-interceptor
Description: A customizable request interceptor for NestJS applications
Latest version: 1.0.1

# @justinjoram/request-interceptor

A customizable request interceptor for NestJS applications that provides request logging and timing functionality.

## Features

- Request logging (method, URL, and body)
- Response logging
- Request timing measurements
- Error logging
- Configurable options

## Installation

```bash
npm install @justinjoram/request-interceptor
```

## Requirements

- NestJS ^10.0.0
- RxJS ^7.8.1

## Usage

### Basic Usage

```typescript
import { RequestInterceptor } from '@justinjoram/request-interceptor';
import { Controller, UseInterceptors } from '@nestjs/common';

@UseInterceptors(new RequestInterceptor())
@Controller('example')
export class ExampleController {
  // Your controller methods
}
```

### With Custom Options

```typescript
import { RequestInterceptor } from '@justinjoram/request-interceptor';
import { Controller, UseInterceptors } from '@nestjs/common';

@UseInterceptors(new RequestInterceptor({
  logging: true,  // Enable/disable request and response logging
  timing: true    // Enable/disable request timing measurements
}))
@Controller('example')
export class ExampleController {
  // Your controller methods
}
```

### Global Registration

```typescript
import { RequestInterceptor } from '@justinjoram/request-interceptor';

// In your main.ts
async function bootstrap() {
  const app = await NestFactory.create(AppModule);
  app.useGlobalInterceptors(new RequestInterceptor());
  await app.listen(3000);
}
```

## Configuration Options

| Option   | Type    | Default | Description                                     |
|----------|---------|---------|------------------------------------------------|
| logging  | boolean | true    | Enables logging of requests and responses       |
| timing   | boolean | true    | Enables logging of request execution time      |

## Logging Output

The interceptor provides the following log information:

- Incoming request details (method, URL, body)
- Response data
- Request execution time (when timing is enabled)
- Error details (if request fails)

## License

MIT

## Contributing

Contributions are welcome! Please feel free to submit a Pull Request.
npm package: @justinjung04/create-react-component
Description: Create React components through CLI
Author: Justin Jung
Latest version: 1.0.1

# Create React Component

Create React components through CLI.

## Install
```
npm install create-react-component --save-dev
```

## Run
```
npx crc
```
or
```
npx create-react-component
```

## Creating

When the question comes up, you can write your component's name
```
Component name(s): MyButton
```

To create multiple components, add the names with comma
```
Component name(s): Header, Body, Footer
```

## Configuration

### crc.config.js

Exports an object with following properties:

- `path` (string): Base path for components to be created. Default is `'src/components'`.
- `component` (string): Type of React component. Accepts one of `'normal'|'pure'|'function'`. Default is `'normal'`.
- `typescript` (boolean): Whether to create TypeScript files. Default is `false`.
- `test` (boolean): Whether to create test file. Default is `false`.
- `stylesheet` (string): Extension of the stylesheet. Accepts one of `'css'|'scss'|'less'|'none'`. Default is `'css'`.
- `custom` (object): To fully customize templates and file componsitions. Accepts following properties:
  - `basePath` (string): Path to custom template folder. Default is `'crc-templates'`.
  - `[templateName]` (array): Array of files to be generated from the custom template. For example, `myTemplate: [ myTemplate.js.js, myTemplate.css.js ]`

### Using custom templates

1. Create template files in a folder. Note the naming convention `[filename].[extension].js`.
```
- my-templates
  - index.js.js
  - index.css.js
```

2. Each template file is a JavaScript that takes `componentName` as argument and returns a new string.
```javascript
module.exports = componentName => (
`console.log(Hello ${componentName}!);`
);
```

3. Add the custom template to `crc.config.js`.
```javascript
module.exports = {
  custom: {
    basePath: 'my-template',
    template1: [
      'index.js',
      'index.css'
    ]
  }
}
```

4. Run the command with `-c` option (or `--custom` option).
```
npx crc -c template1
```

### CLI options

```
Usage: npx crc [options]

Options:

  -v, --version   Prints the version number
  -h, --help      Prints the help message
  -n, --normal    Create component(s) extending React.Component (default)
  -p, --pure      Create component(s) extending React.PureComponent
  -f, --function  Create function component(s)
  -c, --custom    Create custom component(s) based on custom templates
  --javascript    Create JavaScript files (default)
  --typescript    Create TypeScript files
  --test          Include test files
  --notest        Do not include test files (default)
  --css           Inlcude .css file (default)
  --less          Inlcude .less file
  --scss          Inlcude .scss file
  --nocss         Do not inlcude .scss file
  --path          Set path to the component folder
```
npm package: @justinkahrs/on-device-demo
Description: Reusable React mock mobile chat UI with scripted message playback.
Latest version: 0.1.0

# @justinkahrs/on-device-demo

Reusable React component library for rendering a mock mobile chat UI with scripted message playback.

## Install

```bash
npm install @justinkahrs/on-device-demo
```

`react` and `react-dom` are peer dependencies. Most React app templates already include them.

## Quick start

```tsx
import {
  MockMobileDevice,
  type MockMessageScript,
} from "@justinkahrs/on-device-demo";

const script: MockMessageScript[] = [
  { from: "guest", text: "Hey, can you share check-in details?" },
  { from: "bot", text: "Check-in starts at 3:00 PM." },
];

export function Demo() {
  return <MockMobileDevice script={script} messageDelayMs={1200} />;
}
```

## Script format

```tsx
import type { MockMessageScript } from "@justinkahrs/on-device-demo";

const script: MockMessageScript[] = [
  { from: "guest", text: "Hey, can you share check-in details?" },
  {
    id: "main-choice",
    from: "bot",
    awaitUser: true,
    branches: {
      upgrade: "upgrade-path",
      support: "support-path",
    },
    component: <>Need anything else?</>,
  },
  { id: "upgrade-path", from: "guest", text: "Upgrade my checkout time" },
];
```

- `from`: `"guest" | "bot" | "owner"`
- `text`: plain message content
- `component`: custom React node content
- `awaitUser`: pause playback until `resume()` is called
- `id`: optional message id for pointer targets
- `branches`: map from selected value to the next message id/index
- `next`: explicit next message id/index

`QuickReplies` can pass branch values as strings or `{ label, value }`.

## Public exports

- `MockMobileDevice`
- `useMockMobileChat`
- `ChatProvider`
- `Message`, `TypingIndicator`
- `QuickReplies`
- `Header`
- `PhoneContainer`
- `ChatWindow`
- `AppleButton`
- `CommonButton`
- `GuestName`
- `RichLink`
- Types: `MockMessageScript`, `MockMobileDeviceProps`, `QuickReplyOption`, `HeaderProps`

## Local development

```bash
npm install
npm run dev
```

Open:

- `http://localhost:3000` (demo app)
- `http://localhost:3000/library-demo` (library playground)

## Build the library

```bash
npm run build:lib
```

This generates `dist/` (JS + type declarations + CSS module assets).

## Publish to npm

1. Confirm the package name in `/package.json` matches your npm scope.
2. Bump the version: `npm version patch` (or `minor` / `major`).
3. Login once: `npm login`.
4. Publish: `npm publish`.

`prepublishOnly` runs `build:lib` and `npm pack --dry-run`, so publish fails early if packaging is broken.
npm package: @justinkalland/eslint-ts
Description: Node.js lint setup and config that I use in my TypeScript projects (based on StandardJS).
Author: Justin Kalland
Latest version: 2.0.1

# eslint-config-jk-ts
Based on the original [eslint-config-jk](https://github.com/justinkalland/eslint-config-jk), this is the same idea but for TypeScript.

The lint setup and config that I use in my TypeScript projects. Basically StandardJS with a little extra, and linting on pre-commit.

[![JavaScript Style Guide](https://cdn.rawgit.com/standard/standard/master/badge.svg)](https://github.com/standard/standard)

## Setup
One package sets up everything needed for linting:
```
npm i eslint-config-jk-ts --save-dev
```
- Installs [eslint](https://www.npmjs.com/package/eslint)
- Installs the StandardJS eslint configs / plugins
- Installs the TypeScript esling configs / plugins
- Adds [custom rules and plugins I like](https://github.com/justinkalland/eslint-config-jk-ts/blob/master/index.js)
- Installs [husky](https://www.npmjs.com/package/husky)
- Installs [lint-staged](https://www.npmjs.com/package/lint-staged)
- [Adds](https://github.com/justinkalland/eslint-config-jk-ts/blob/master/scripts/postInstall.js) to `package.json` (if file exsists)
  - Eslint config option
  - Husky hook to lint on pre-commit
  - package script `lint` (`npm run lint`)
npm package: @justinli/create-vite-template
Description: This template provides a minimal setup for a static site using:
Latest version: 0.1.4

# Create Vite Template

This template provides a minimal setup for a static site using:

- React
- TypeScript
- Vite
- Oxlint
- Oxfmt

## Prerequisites

- Node.js
- pnpm

## Usage

Create a project in a new directory:

```
pnpm create @justinli/vite-template my-app
```

Create a project in the current (empty) directory:

```
pnpm create @justinli/vite-template .
```

cd into the project directory, install dependencies, and start the development server:

```
cd my-app
pnpm install
pnpm dev
```

## Scripts

- `pnpm dev`: Start the development server
- `pnpm build`: Build for production
- `pnpm preview`: Preview the production build locally
- `pnpm lint`: Run Oxlint to check for linting errors
- `pnpm lint:fix`: Run Oxlint to fix linting errors
- `pnpm fmt`: Run Oxfmt to format code
- `pnpm fmt:check`: Run Oxfmt to check if code is formatted
- `pnpm check`: Run TypeScript, Oxlint, and Oxfmt checks
npm package: @justinlwz/react-scripts
Description: Configuration and scripts for Create React App.
Latest version: 1.2.7

># Deprecated warning
> This is deprecated now that Create React App 2 support SCSS.

# react-scripts

This package includes scripts and configuration used by [Create React App](https://github.com/facebookincubator/create-react-app).<br>
Please refer to its documentation:

* [Getting Started](https://github.com/facebookincubator/create-react-app/blob/master/README.md#getting-started) – How to create a new app.
* [User Guide](https://github.com/facebookincubator/create-react-app/blob/master/packages/react-scripts/template/README.md) – How to develop apps bootstrapped with Create React App.

#### Installation with Create React App:

NPM 5.2 and higher:
```sh
npx create-react-app app-name --scripts-version @justinlwz/react-scripts
```

Older versions:
```sh
npm create-react-app app-name --scripts-version @justinlwz/react-scripts
```

#### Migrating versions

Inside any created project that has not been ejected, run:

```sh
npm install --save --save-exact @justinlwz/react-scripts@<version>
```

#### Important Note:
This modification removed default prebuilt set up for autoprefixing to give you the control in setting up your browser support. To find out more, refer to the [Browserlist Docs](https://github.com/ai/browserslist/blob/master/README.md#environments) to learn how to set up a `.browserslistrc` config.

#### What is changed:
The package adds the ability to process SCSS and moved prefixing to be controled using a `.browserslistrc` file instead of having it be done via the webpack configuration. Other areas are currently left intact for easy compatibility with any upgrades made by Facebook Create React App's team. This fork also branches from `master` rather than the `next` branch to ensure stability when used in a production environment.

#### Motivation of Fork:
While `Create React App` is a fantastic way to get started with React projects, the SCSS support out of the box makes it quite difficult to use it in conjunction with other SCSS-based UI libraries, including the in-house library we use at Bananatag. This fork include changes made to the Webpack configuration to support SCSS and external UI libraries.
npm package: @justinm/eslint-config
Description: A custom eslint config curated by Justin McCormick.
Author: Justin McCormick
Latest version: 0.0.0

## eslint-config-justinm

An eslint config curated by Justin McCormick, a Systems Architect based near Indianapolis, Indiana.

<div style="text-align: center;">

[![Contributors][contributors-shield]][contributors-url]
[![Forks][forks-shield]][forks-url]
[![Stargazers][stars-shield]][stars-url]
[![Issues][issues-shield]][issues-url]
[![MIT License][license-shield]][license-url]

</div>

**Table of Contents**

<!-- toc -->

- [Installing](#Installing)
- [Configuring Eslint](#configuring-eslint)

<!-- tocstop -->


## Installing

```shell
npm install --save-dev eslint-config-justinm

# or using Yarn

yarn add -D eslint-config-justinm
```

## Configuring Eslint

```javascript
module.exports = {
  extends: [
    // @justinm provides a very minimal config
    "@justinm",
    // or choose the recommended config
    "@justinm/eslint-config/recommended",
    
    // Next, choose one of the following based on your project's language
    "@justinm/eslint-config/node",
    "@justinm/eslint-config/typescript",

    // Add additional styling support
    "@justinm/eslint-config/prettier",
    "@justinm/eslint-config/sorted",
  ]
}
```

[contributors-shield]: https://img.shields.io/github/contributors/justinm/eslint-config-justinm.svg?style=for-the-badge
[contributors-url]: https://github.com/justinm/eslint-config-justinm/graphs/contributors
[forks-shield]: https://img.shields.io/github/forks/justinm/eslint-config-justinm.svg?style=for-the-badge
[forks-url]: https://github.com/justinm/eslint-config-justinm/network/members
[stars-shield]: https://img.shields.io/github/stars/justinm/eslint-config-justinm.svg?style=for-the-badge
[stars-url]: https://github.com/justinm/eslint-config-justinm/stargazers
[issues-shield]: https://img.shields.io/github/issues/justinm/eslint-config-justinm.svg?style=for-the-badge
[issues-url]: https://github.com/justinm/eslint-config-justinm/issues
[license-shield]: https://img.shields.io/github/license/justinm/eslint-config-justinm.svg?style=for-the-badge
[license-url]: https://github.com/justinm/eslint-config-justinm/blob/master/LICENSE.md