open-index/open-npm huggingface dataset:
npm package: @hiperative/eslint-config
Description: Hiperative's default ESLint config
Author: Rafaell Lycan
Latest version: 1.0.0

# @hiperative/eslint-config

Hiperative's base ESLint config.

## Installation

```sh
npm install --save-dev eslint @hiperative/eslint-config

# OR

yarn add --dev eslint @hiperative/eslint-config
```

## Usage

After installing, update your project's `.eslintrc` file to import the rule sets
you want:

```json
{
  "extends": ["@hiperative/eslint-config"]
}
```

### TypeScript support

You can also enable by installing `typescript` and using as:

```json
{
  "extends": ["@hiperative/eslint-config/typescript"]
}
```

---

Read the
[ESlint config docs](http://eslint.org/docs/user-guide/configuring#extending-configuration-files)
for more information.
npm package: @hiperative/prettier-config
Description: Hiperative's default Prettier config
Author: Rafaell Lycan
Latest version: 1.0.0

# @hiperative/prettier-config

Hiperative's base Prettier config.

## Installation

```sh
npm install --save-dev prettier @hiperative/prettier-config

# OR

yarn add --dev prettier @hiperative/prettier-config
```

## Usage

If you don't plan on changing the config at all, the easiest way to install is
to use the
[`prettier` parameter](https://prettier.io/docs/en/configuration.html#sharing-configurations)
in `package.json`:

```json
{
  "name": "your-awesome-app",
  "prettier": "@hiperative/prettier-config"
}
```

If you need to extend or change the config, you can update your project's
`prettier.config.js` file to import the rule sets you want:

```js
module.exports = {
  ...require('@hiperative/prettier-config'),
  // your overrides here
}
```

---

Read the [Prettier config docs](https://prettier.io) for more information.
npm package: @hiperative/tsconfig
Description: Hiperative's default tsconfigs
Author: Rafaell Lycan
Latest version: 1.0.0

# @hiperative/tsconfig

A collection of different base `tsconfig.json` for Hiperative projects.

This project aims to reduce per-project configuration as much as possible. With
good defaults, we can focus on building, not configuration!

## Installation

```sh
npm install --save-dev @hiperative/tsconfig

# OR

yarn add --dev @hiperative/tsconfig
```

## Usage

After installing, update your project's `tsconfig.json` file with it:

```json
{
  "extends": "@hiperative/tsconfig"
  // your overrides here
}
```

_You can also extend from `@hiperative/tsconfig/recommended` with has a more
strict configuration._

Note that you'll have to provide a significant amount of project-specific
configuration options, including the `outDir` and `include` files.

## Contributing

Try to optimize for the fewest specified options between the config
specializations. For example, only `app` has `noEmit: true`, since the [default
value][compiler options], `false`, it's good for the `lib` config. Specifying it
only in the `app` config means fewer overall entries!

We want to keep maintenance low by only specifying what is necessary. If the
option's [default value][compiler options] is good for every config, remove it
from every config!

[compiler options]:
  https://www.typescriptlang.org/docs/handbook/compiler-options.html