open-index/open-npm huggingface dataset:
npm package: @peakfijn/config-eslint
Description: Sharable configuration for ESLint with Peakfijn conventions
Author: Cedric van Putten
Latest version: 2.1.0
Deprecated: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.

# ESLint - Peakfijn

A sharable [ESLint](https://github.com/eslint/eslint) configuration with Peakfijn conventions.

## Installation

Install the dependency with npm.

```bash
$ npm install --save-dev @peakfijn/config-eslint
```

## Configuration

Update the `package.json` to include an [eslintConfig](https://eslint.org/docs/user-guide/configuring) property.

```json
{
	"eslintConfig": {
		"extends": "peakfijn"
	}
}
```

## Usage

After installing and configuring the package, you can use it by running this command.

```bash
$ npx eslint 'src/**/*.js'
```

## License

The MIT License (MIT). Please see [License File](LICENSE.md) for more information.
npm package: @peakfijn/config-release
Description: Sharable configuration for Semantic Releases with basic open source projects
Author: Cedric van Putten
Latest version: 2.1.0
Deprecated: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.

# Basic - Peakfijn Releases

A sharable [Semantic Releases](https://github.com/semantic-release/semantic-release) configuration for basic open source projects.

## Installation

Install the dependency with npm.

```bash
$ npm install --save-dev @peakfijn/config-release
```

## Configuration

Update the `package.json` to include a [release](https://github.com/semantic-release/semantic-release/blob/caribou/docs/usage/configuration.md#configuration) property.

```json
{
	"release": {
		"extends": "@peakfijn/config-release"
	}
}
```

And make sure `package.json` also contains the basic repository (**git url**) information.

```json
{
	"name": "<project>",
	"version": "0.0.0",
	"repository": {
		"type": "git",
		"url": "https://github.com:peakfijn/<project>.git"
	}
}
```

## Usage

After installing and configuring the package, you can use it by running this command.

```bash
$ npx semantic-release
```

## License

The MIT License (MIT). Please see [License File](LICENSE.md) for more information.
npm package: @peakfijn/config-release-react
Description: Sharable configuration for Semantic Releases with React
Author: Cedric van Putten
Latest version: 2.1.0
Deprecated: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.

# React - Peakfijn Releases

A sharable [Semantic Releases](https://github.com/semantic-release/semantic-release) configuration for [plain React](https://github.com/facebook/create-react-app) projects.

## Installation

Install the dependency with npm.

```bash
$ npm install --save-dev @peakfijn/config-release-react
```

## Configuration

Update the `package.json` to include a [release](https://github.com/semantic-release/semantic-release/blob/caribou/docs/usage/configuration.md#configuration) property.

```json
{
	"release": {
		"extends": "@peakfijn/config-release-react"
	}
}
```

And make sure `package.json` also contains the basic repository (**git url**) information.

```json
{
	"name": "<project>",
	"version": "0.0.0",
	"repository": {
		"type": "git",
		"url": "git@bitbucket.org:peakfijn/<project>.git"
	}
}
```

## Usage

After installing and configuring the package, you can use it by running this command.

```bash
$ npx semantic-release
```

## License

The MIT License (MIT). Please see [License File](LICENSE.md) for more information.
npm package: @peakman/dagger.js
Description: A html-based runtime web frontend framework
Author: Tony Peakman
Latest version: 0.9.21

dagger.js is a lightweight html-based runtime web frontend framework.  
Please find the document and examples at [https://daggerjs.org](https://daggerjs.org/).  
Please find the github link at [here](https://github.com/dagger8224/dagger.js).
npm package: @peakydicers/good-env-validator
Description: Validate your environment variables like a king.
Author: peakyDicers
Latest version: 1.0.2

# GOOD ENV VALIDATOR

Okay. So, you've got environment variables, some are required for development, some for staging and some for prod. How do you handle this?

You use **GOOD-ENV-VALIDATOR**.

With good-env-validator, you specify what env vars exist, and whether they're required in dev, staging and prod. Then in a single function call, you can check whether or not your environment is valid.

Used with https://github.com/motdotla/dotenv.

The only requirement is that you need the environment variable `APP_ENV` set to `development`, `staging` or `production`.

```typescript
import { validate } from "good-env-validator";

const myRequirements = [
  {
    name: "PORT",
    required: {
      dev: true,
      staging: true,
      prod: false,
    },
  },
  {
    name: "SOME_OTHER_FLAG",
    required: {
      dev: true,
      staging: false,
      prod: false,
    },
  },
];

try {
  validate(myRequirements);
} catch (err) {
  if (err.name === "INVALID_APP_ENV") {
    console.error(
      "process.env.APP_ENV must be set to development, staging or production"
    );
  } else if (err.name === "VARS_MISSING") {
    err.missing.forEach((name) => {
      console.error(`Env var ${name} is required for ${process.env.APP_ENV}`);
    });
  }
  process.exit(1);
}
```