open-index/open-npm huggingface dataset:
npm package: @rtvision/esbuild-dynamic-import
Description: Plugin for transform dynamic imports in esbuild
Author: Kalvens
Latest version: 2.0.2

# Esbuild Dynamic Import

[![Version](https://img.shields.io/npm/v/@rtvision/esbuild-dynamic-import.svg)](https://npmjs.org/package/@rtvision/esbuild-dynamic-import)
[![Downloads/week](https://img.shields.io/npm/dw/@rtvision/esbuild-dynamic-import.svg)](https://npmjs.org/package/@rtvision/esbuild-dynamic-import)
[![License](https://img.shields.io/npm/l/@rtvision/esbuild-dynamic-import.svg)](https://github.com/RtVision/esbuild-dynamic-import/blob/master/package.json)

### Features

-Transforms dynamic imports that contain a template string variable into static imports to be processed by esbuild

-Rewrites dynamic imports of js files that contain a template string variable to use absolute path instead

## Install

```sh
npm i @rtvision/esbuild-dynamic-import
```

I know this was working using the version 0.13.14 of esbuild. It may work for earlier versions depending on when the plugin system was implemented

## Example Usage

```js
import DynamicImport from '@rtvision/esbuild-dynamic-import';
DynamicImport({ transformExtensions: ['.vue'], changeRelativeToAbsolute: true, filter: /src\/.*\.js$/ }),
```

## Parameters

### transformExtensions

Transforms all dynamic imports that contain a template varable and the imported file extension
is included in transformExtensions. I.E. ` import(``../../${file}.vue``) `
All imports found will be turned into static imports of every possible valid import it could be.
It then uses the static imports instead of node dynamically importing the file at runtime

My use case for this was I wanted esbuild to process the possible imports that are
.vue (SFC vue) files so they can be processed by the EsbuildVue plugin and made into
valid javascript that nodejs can run.

### changeRelativeToAbsolute

If there exists a dynamic import like ` import(``../../${file}.js``) `
then that in theory could be resolved at runtime just fine by nodejs. The main
issue is that the relative file path is now different due to the bundled file produced by
esbuild being in a likely different file location. changeRelativeToAbsolute will fix this issue
by changing all relative dynamic imports that contain a template literal variable to absolute ones.

For my use case dynamic imports while using vite are needed to be relative for production builds
especially since Rollup is currently used and Rollup requires all dynamic imports to be relative.

### Filter

The Filter parameter is used to reduce the scope of the file search.

I set it to just search our local source directory, but by default it will search through every
js file that is not marked as external

### Loader

Need to specify if you need one of esbuild's internal loaders to transform the file after
the dynamic imports are handled by this plugin. i.e. if your filter is /\.jsx$/ then you need to specify jsx as your loader

## License

MIT © RtVision
npm package: @rtvu/registration-logger
Description: A registration style logger written in Typescript.
Author: Ryan Vu
Latest version: 1.0.1

# REGISTRATION-LOGGER

A registration style logger written in Typescript.

## Installation

To install run:

```bash
npm install @rtvu/registration-logger
```

## Concepts

Designed for easy debug logging.

`LogKey`s are the central control structure. All logging requires a key as an argument. Logging at a priority level is enabled when provided key has already been registed with a permitted level. The key registration and permitted level can be bypassed by using the override.

`LogKey`s are objects with either a `description` or `name` string property. `name` property allows using functions as keys.

## Basic Usage

```typescript
import { logAddKey, logInfo, LogLevel} from `@rtvu/registration-logger`

key = { description: "key" }
logAddKey(key, LogLevel.Info)

logInfo(key, "Hello World!") // > "Info: key: Hello World!"
```

## Usage in a Module

```typescript
import { logAddKeys, logUpdateKeys, logInfo, LogLevel} from `@rtvu/registration-logger`

// Specify level for each function
logAddKeys([
  [foo, LogLevel.Off],
  [bar, LogLevel.Debug],
])

// Overrides function level if module has lower priority
const moduleLogLevel = LogLevel.Off
if (moduleLogLevel !== LogLevel.Off) {
  logUpdateKeys([
    [foo, moduleLogLevel],
    [bar, moduleLogLevel],
  ])
}

export function foo() {
  logInfo(foo, "foo") // Logging disabled
}

export function bar() {
  logInfo(bar, "bar") // Logging enabled at `Debug` priority
}
```

## Usage With Override

```typescript
import { logInfo, logSetOverrideLevel, LogLevel} from `@rtvu/registration-logger`

export function foo() {
  logInfo(foo, "foo")
}

foo() // Logging disabled, key is not registered

logSetOverrideLevel(LogLevel.Info)

foo() // > "(Override): Info: foo: foo"

logSetOverrideLevel(LogLevel.Off)

foo() // Logging disabled, key is not registered

```
npm package: @rtw_np/mui-theme-config
Description: This package provides a shareable MUI theme configuration that can be used across multiple projects.
Author: rtw
Latest version: 2.6.1

# MUI Config

This package provides a shareable MUI theme configuration that can be used across multiple projects.

## Installation

```bash
npm install @rtw_np/mui-theme-config
yarn add @rtw_np/mui-theme-config
```

## Components

This package includes the following components:

**AppPagination**:
> A comprehensive pagination component built on top of MUI's Pagination. It offers standard page navigation, an item
> range display (e.g., "Showing 1-10 of 50"), an optional `pageSize` selector, and responsive design.

**FilterForm**:
> A flexible form component integrated with Formik, designed for creating filter interfaces. It supports submission (
> search) and reset functionalities, along with customizable layouts and actions.

**FormInput**:
> A layout component for structuring form inputs. It handles the display of labels, input fields, and error messages,
> with options for vertical or horizontal label alignment.

**MobileBreakpointProvider**:
> A provider component that detects and supplies information about the current screen size (mobile or tablet) to its
> children, utilizing MUI's breakpoint system. This allows for responsive rendering of child components.