open-index/open-npm huggingface dataset:
npm package: @hollowverse/common
Description: Common configurations, helper functions and code quality scripts for Hollowverse repos
Latest version: 3.2.7

`@hollowverse/common`
=================================================================

This repository contains shared configuration files, utility functions and code quality scripts used across multiple [Hollowverse](https://github.com/hollowverse) repositories.

## Configuration Files
`common` currently includes configuration files for:

* TypeScript ([`tsconfig.json`](./tsconfig.json))
* TSLint ([`tslint.json`](./tslint.json))
* ESLint ([`.eslintrc.json`](./.eslintrc.json))
* Stylelint ([`.stylelintrc`](./.stylelintrc))

### How to use the shared configuration

1. Install this package as dependency of your project:
     
     ```bash
     yarn add @hollowverse/common --dev
     # or
     npm install @hollowverse/common --save-dev
     ```
2. Install the [peer dependencies](./package.json#L64) for each of the tools used in the new project.
3. Extend your project configuration files with the corresponding files from this package. For example, here is how to extend `tsconfig.json`:
    
    ```json
    {
      "extends": "./node_modules/@hollowverse/common/tsconfig.json"
    }
    ```
   Refer to each tool's documentation for more information on how to extend the configuration.
4. Add properties to the configuration file to override the shared configuration as needed.

## Helper Functions

In addition to shared configuration files, `common` also provides a set of utility functions used in multiple repositories in the Hollowverse organization for deployment and other tasks, the functions are exported from the [`./helpers`](./helpers) directory.

Refer to the [`deploy.js`](https://github.com/hollowverse/hollowverse/tree/master/deploy.js) script of [hollowverse/hollowverse](https://github.com/hollowverse/hollowverse) for examples on how to use these functions.
npm package: @hollowverse/config
Description: Common configurations for Hollowverse repos
Latest version: 42.0.0

# `@hollowverse/config` [![Build Status](https://travis-ci.org/hollowverse/config.svg?branch=master)](https://travis-ci.org/hollowverse/config)

This repository contains shared configuration files used across multiple [Hollowverse](https://github.com/hollowverse) repositories.

## Configuration Files

`@hollowverse/config` currently includes configuration files for:

- TypeScript ([`tsconfig.json`](./tsconfig.json))
- TSLint ([`tslint.json`](./tslint.json))
- ESLint ([`.eslintrc.json`](./.eslintrc.json), other language-specific configurations in [`./eslint`](./eslint))
- Stylelint ([`.stylelintrc`](./.stylelintrc))
- Prettier ([`prettier.config.js`](./prettier.config.js))
- Babel ([`lambda/.babelrc`](./lambda/.babelrc) for AWS Lambda)

### How to use the shared configuration

1.  Install this package as dependency of your project:
    ```bash
    yarn add @hollowverse/config --dev
    # or
    npm install @hollowverse/config --save-dev
    ```
2.  Install the [peer dependencies](./package.json#L31) for each of the tools used in the new project.
3.  Extend your project configuration files with the corresponding files from this package. For example, here is how to extend `tsconfig.json`:
    ```json
    {
      "extends": "./node_modules/@hollowverse/config/tsconfig.json"
    }
    ```
    Refer to each tool's documentation for more information on how to extend the configuration.
4.  Add properties to the configuration file to override the shared configuration as needed.

---

[If you need help or wanna get in touch...](https://github.com/hollowverse/hollowverse/wiki/Help)
npm package: @hollowverse/utils
Description: Common helper functions and code quality scripts for Hollowverse repos
Latest version: 8.0.0

# `@hollowverse/utils` [![Build Status](https://travis-ci.org/hollowverse/utils.svg?branch=master)](https://travis-ci.org/hollowverse/utils)

This package provides a set of utility functions used in multiple repositories in the Hollowverse organization for deployment and other tasks, the functions are exported from the [`./helpers`](./helpers) directory.

Refer to the [`deploy.js`](https://github.com/hollowverse/hollowverse/tree/master/deploy.js) script of [hollowverse/hollowverse](https://github.com/hollowverse/hollowverse) for examples on how to use these functions.

---

[If you'd like to tell us something, or need help with anything...](https://github.com/hollowverse/hollowverse/wiki/Help)
npm package: @hollowverse/validate-filenames
Description: CLI for validating filenames in a directory according to customizable rules
Author: Hollowverse
Latest version: 3.0.2

# `@hollowverse/validate-filenames` [![Build Status](https://travis-ci.org/hollowverse/validate-filenames.svg?branch=master)](https://travis-ci.org/hollowverse/validate-filenames)

You can use this package to validate that the filenames in your git repository
meet your validation rules.

Current validation rules are `camelCase`, `PascalCase`, and `ignore`.

## Installation

```bash
yarn add @hollowverse/validate-filenames
```

## Add as an npm script

In your `package.json`

```json
{
  "scripts": {
    "validate-filenames": "validate-filenames"
  }
}
```

## Usage

In a git-managed repo run:

```bash
yarn validate-filenames
```

When you do that, the tool will retrieve a list of all the filenames under git
control and will validate them based on the rules that you have in your config
file.

## Config file

You can configure validate-filenames by dropping a file called `validateFilenames.json`
or `validateFilenames.js` at the root of your repo.

validate-filenames can be configured as follows

```json
{
  "rules": [
    {
      "validation": "camelCase",
      "patterns": ["**/*"]
    },
    {
      "validation": "ignore",
      "patterns": [
        "README.md",
        "Dockerfile",
        "LICENSE.md",
        "customTypings/*",
        "typings/*"
      ]
    }
  ]
}
```

If you're using the `js` version of the configurations, you need to export an object such as the above.

Notice that `rules` is an array. Each item in the array is an object with two
properties: `validation` and `patterns`.

#### `validation`

`validation` can be one of three values: `camelCase`, `PascalCase`, or `ignore`.

#### `patterns`

`patterns` is an array of
[glob patterns](https://github.com/isaacs/node-glob#glob-primer) that tells
`validate-filenames` that the validation rule applies to files that fall within
this glob pattern.

#### Rule order

The order of the rules matter. The last rule wins. This allows us to have
general rules and override those general rules with specific rules for specific
paths. In the example above, we're saying all filenames within our repo should
be camelCased except for certain files which should be ignored.

## For issues or questions

A lot of the above may very well not make much sense. So feel free to post issues or questions here:

https://github.com/hollowverse/hollowverse/issues