open-index/open-npm huggingface dataset:
npm package: @404love/next
Description: Next.js helpers for 404found.love
Author: Dario Rapisardi
Latest version: 0.2.3

# @404love/next

Next.js helpers for integrating [404found.love](https://404found.love) in App Router projects.

## Install

```bash
npm install @404love/next
```

## Requirements

- Next.js 13.4+ App Router
- React 18+

## Quick start

Create `app/not-found.tsx`:

```tsx
import { createNotFoundPage } from "@404love/next"

export default createNotFoundPage()
```

This renders a full-page iframe pointing to `https://404found.love/frame`, plus an optional
top-level back link outside the iframe.

## Options

```tsx
import { createNotFoundPage } from "@404love/next"

export default createNotFoundPage({
  includeBackLink: true,
  backLinkLabel: "Back to site",
  query: { source: "app-router" },
  iframeTitle: "404 Love Found",
  syncFrameBackground: true,
})
```

### Option reference

- `baseUrl`: override the default `https://404found.love/frame`.
- `referer`: override the detected referrer.
- `syncFrameBackground`: post the host background color to the iframe (default: true).
- `frameBackgroundTargetOrigin`: override the `postMessage` target origin for background sync (defaults to `https://404found.love`, disabled for other origins).
- `includeBackLink`: show or hide the top-level back link.
- `backLinkLabel`: custom label for the back link.
- `backLinkClassName`, `backLinkStyle`: customize the back link.
- `containerClassName`, `containerStyle`: customize the wrapper.
- `iframeClassName`, `iframeStyle`, `iframeTitle`, `iframeProps`: customize the iframe.
- `query`: extra query parameters (e.g. `{ source: "app-router" }`).

### Full options example

```tsx
import { createNotFoundPage } from "@404love/next"

export default createNotFoundPage({
  baseUrl: "https://404found.love/frame",
  referer: "https://example.com/marketing",
  syncFrameBackground: true,
  frameBackgroundTargetOrigin: "https://404found.love",
  includeBackLink: true,
  backLinkLabel: "Return to site",
  backLinkClassName: "notfound-back-link",
  backLinkStyle: {
    color: "#0b3b2e",
    background: "rgba(255, 255, 255, 0.92)",
    border: "1px solid rgba(11, 59, 46, 0.2)",
  },
  containerClassName: "notfound-container",
  containerStyle: {
    background: "linear-gradient(180deg, #fef6ef, #fff)",
  },
  iframeClassName: "notfound-frame",
  iframeStyle: {
    borderRadius: "16px",
    boxShadow: "0 18px 44px rgba(0, 0, 0, 0.12)",
  },
  iframeTitle: "404 Love Found",
  iframeProps: {
    loading: "lazy",
    allow: "fullscreen",
    referrerPolicy: "no-referrer",
  },
  query: { source: "app-router", campaign: "spring-2026" },
})
```

## Back navigation

The package passes a `referer` query param using server headers and the client
`document.referrer`, then renders a top-level back link outside the iframe. That link
navigates the host history (or the detected referrer) so the user exits the iframe.

## Example app

See the repository for a minimal Next.js example in `examples/basic`.

## License

MIT
npm package: @47ng/check-env
Description: Check that the critical environment variables are set
Author: François Best
Latest version: 3.0.0

<h1 align="center"><code>@47ng/check-env</code></h1>

<div align="center">

[![NPM](https://img.shields.io/npm/v/@47ng/check-env?color=red)](https://www.npmjs.com/package/@47ng/check-env)
[![MIT License](https://img.shields.io/github/license/47ng/check-env.svg?color=blue)](https://github.com/47ng/check-env/blob/next/LICENSE)
[![CI/CD](https://github.com/47ng/check-env/workflows/CI%2FCD/badge.svg?branch=next)](https://github.com/47ng/check-env/actions)
[![Coverage Status](https://coveralls.io/repos/github/47ng/check-env/badge.svg?branch=next)](https://coveralls.io/github/47ng/check-env?branch=next)

</div>

<p align="center">
  Check that the critical environment variables are set for your app,
  and that you did not leave dangerous development overrides in production.
</p>

## Installation

```
yarn add @47ng/check-env
```

## Usage

```js
import { checkEnv } from '@47ng/check-env'

checkEnv({
  // Will log an error and throw if any of these are missing:
  required: [
    'SOME_API_SECRET',
    'PRIVATE_TOKEN',
    'SOME_OTHER_IMPORTANT_THING'
    // ...
  ],

  // Will log an error and throw if any of these are set in production:
  unsafe: [
    'LOCAL_OVERRIDE_DISABLE_HTTPS',
    'INSECURE_COOKIES'
    // ...
  ]
})
```

If some required environment variable are not set, it will tell you and throw
an error at the end:
!["CLI output"](output.png)

## Error handling

You can choose to skip throwing an error with the `noThrow` option:

```js
checkEnv({
  noThrow: true,
  ...
})
```

## Conditional Checks

If you want to require some variables only in production, you can add a condition
before the variable name, any falsy value will be ignored:

```ts
const __PROD__ = process.env.NODE_ENV === 'production'

checkEnv({
  required: [
    'ALWAYS_REQUIRED',
    __PROD__ && 'ONLY_REQUIRED_IN_PRODUCTION',
    !__PROD__ && 'YOU_GET_THE_IDEA'
  ]
})
```

## Logging

By default, `check-env` uses `console.err` with emoji.

You can override the default logging methods with `logMissing` and `logUnsafe`.

Example using [Pino](https://github.com/pinojs/pino):

```js
const logger = require('pino')()

checkEnv({
  logMissing: name => logger.error(`Missing required environment variable ${name}`),
  logUnsafe: name => logger.warn(`Unsafe environment variable ${name} set in production`),
  ...
})
```

## License

[MIT](https://github.com/47ng/check-env/blob/master/LICENSE) - Made with ❤️ by [François Best](https://francoisbest.com)

Using this package at work ? [Sponsor me](https://github.com/sponsors/franky47) to help with support and maintenance.
npm package: @4geit/rct-data-table-component
Description: data table component for react apps
Author: Caner Candan
Latest version: 1.103.2

# @4geit/rct-data-table-component [![npm version](//badge.fury.io/js/@4geit%2Frct-data-table-component.svg)](//badge.fury.io/js/@4geit%2Frct-data-table-component)

---

data table component for react apps

## Demo

A live storybook is available to see how the component looks like @ http://rct-data-table-component.ws3.4ge.it

## Installation

1. A recommended way to install ***@4geit/rct-data-table-component*** is through [npm](//www.npmjs.com/search?q=@4geit/rct-data-table-component) package manager using the following command:

```bash
npm i @4geit/rct-data-table-component --save
```

Or use `yarn` using the following command:

```bash
yarn add @4geit/rct-data-table-component
```

Make sure you also have those tools installed globally in your system since @4geit/rct-data-table-component requires them to work properly:

* create-react-app: `sudo npm i -g create-react-app`
* storybook: `sudo npm i -g @storybook/cli`

2. Depending on where you want to use the component you will need to import the class `RctDataTableComponent` to your project JS file as follows:

```js
import RctDataTableComponent from '@4geit/rct-data-table-component'
```

For instance if you want to use this component in your `App.js` component, you can use the RctDataTableComponent component in the JSX code as follows:

```js
import React from 'react'
// ...
import RctDataTableComponent from '@4geit/rct-data-table-component'
// ...
const App = () => (
  <div className="App">
    <RctDataTableComponent/>
  </div>
)
```

## Usage

1. You can actually use the component `rct-data-table-component` alone by running the command:

```bash
yarn start
```

Make sure the dependencies are all installed by running the command `yarn`.

2. `rct-data-table-component` comes along with `storybook` already setup therefore you can use it by running the command:

```bash
yarn storybook
```

The storybook is also deployed online and available @ http://rct-data-table-component.ws3.4ge.it
npm package: @4geit/rct-ng-vendor
Description: gather all the packages vendor modules
Author: Caner Candan
Latest version: 1.101.2

# @4geit/rct-ng-vendor [![npm version](//badge.fury.io/js/@4geit%2Frct-ng-vendor.svg)](//badge.fury.io/js/@4geit%2Frct-ng-vendor)

---

This package gathers all the common vendor modules so we avoid duplication of dependencies when loading several components into an old web application architecture that does not support import/export module feature.

## Installation

1. A recommended way to install ***@4geit/rct-ng-vendor*** is through [npm](//www.npmjs.com/search?q=@4geit/rct-ng-vendor) package manager using the following command:

```bash
npm install @4geit/rct-ng-vendor
```

Or use `yarn` using the following command:

```bash
yarn add @4geit/rct-ng-vendor
```
npm package: @4lch4/busylight
Description: My personal library for interacting with my Kuando Busylight.
Author: 4lch4
Latest version: 1.3.1
Deprecated: I've moved all of my Busylight packages to the @k-blight scope.

# @4lch4/busylight

This is a simple library to control a Busylight device from [Plenom][0], using their HTTP app.

## Requirements

In order for this to work, you have to have the official Busylight HTTP app installed and running on your computer. Here are the two ways I'm aware of to get it:

1. From [the Development Tools section of the download software page][2]. You have to request it though.
2. From the same download software page linked just above, but under the Premium Software you want to download the one for Twilio. The zip provided will include the HTTP app.

## Usage

```typescript
import { Busylight } from '@4lch4/busylight'

const busylight = new Busylight()

await busylight.on('green')

await busylight.alert({ color: 'red', sound: 7, volume: 50 })

await busylight.blink('blue')

await busylight.jingle({ color: 'purple', sound: 3, volume: 100 })

await busylight.pulse('yellow')

await busylight.flashColors('red', 'blue')

await busylight.off()
```

## Further Reading

For more information, refer to [the manual][1] from Kuando on the HTTP app, it's where the API documentation resides.

[0]: https://www.plenom.com
[1]: https://www.plenom.com/wp-content/uploads/2020/01/kuandoHUB-Manual-0.9-Rev.0.9.19.pdf
[2]: https://www.plenom.com/downloads/download-software