# tslint-luhis

> Luhis's custom TSLint Rules

Latest version **0.0.0-alpha0003** (published 2019-02-09) · MIT license · 0 weekly downloads

## Install

```sh
npm install tslint-luhis
pnpm add tslint-luhis
yarn add tslint-luhis
bun add tslint-luhis
```

## Health

**Score 15/100 (F)** — status: abandoned.

Positive: no vulnerabilities.

Warnings: low downloads; no types; no esm support; pre 1.0.

Negative: abandoned; low maintenance score.

## Facts

| | |
|---|---|
| Version | 0.0.0-alpha0003 |
| Published | 2019-02-09 |
| First published | 2019-01-26 |
| Weekly downloads | 0 |
| License | MIT |
| TypeScript types | none |
| Module format | CommonJS |
| Dependencies | 0 |
| Unpacked size | 5.4 KB |
| Known vulnerabilities | 0 |
| Install scripts | no |
| GitHub stars | 0 |
| Author | Matt McCorry |
| Maintainers | mccorry |

## Links

- npm: https://www.npmjs.com/package/tslint-luhis
- Repository: https://github.com/luhis/tslint-luhis
- Homepage: https://github.com/luhis/tslint-luhis#readme
- Issues: https://github.com/luhis/tslint-luhis/issues
- npm.io page: https://npm.io/package/tslint-luhis

## Recent versions

- 0.0.0-alpha0003 (latest) — 2019-02-09
- 0.0.0-alpha0002 — 2019-01-26
- 0.0.0-alpha0001 — 2019-01-26

## README

# tslint-luhis

## Background

Whist working on a React higher order component library I ran into an issue where it created components that functioned correctly, but behaved less than perfectly when inspected in debug mode with the React Dev Tools.  This is easily fixed, but it leaves with code that is more verbose than some would normally write.  This package contains a rule to cover that instance to ensure that names are given to React components.

## Installing

`npm install tslint-luhis --save-dev`

Then add the ruleset to your tslint.json configuration:

`"extends": [
        "tslint:recommended",
        "tslint-luhis"
    ],`

---
_Source: https://npm.io/package/tslint-luhis · Machine-readable twin of the npm.io package page. Health data is recomputed on every publish._