# liw-components

> Altiore React Components - Life Is Wonderful

Latest version **2.3.46** (published 2019-02-28) · MIT license · 0 weekly downloads

## Install

```sh
npm install liw-components
pnpm add liw-components
yarn add liw-components
bun add liw-components
```

## Health

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

Positive: has types; no vulnerabilities.

Warnings: low downloads; no esm support.

Negative: abandoned; low maintenance score.

## Facts

| | |
|---|---|
| Version | 2.3.46 |
| Published | 2019-02-28 |
| First published | 2018-06-11 |
| Weekly downloads | 0 |
| License | MIT |
| TypeScript types | bundled |
| Module format | CommonJS |
| Dependencies | 1 |
| Unpacked size | 120 KB |
| Known vulnerabilities | 0 |
| Install scripts | no |
| GitHub stars | 0 |
| Author | Altiore |
| Maintainers | altiore |

## Links

- npm: https://www.npmjs.com/package/liw-components
- Repository: https://github.com/altiore/react-components
- Homepage: https://github.com/altiore/react-components#readme
- Issues: https://github.com/altiore/react-components/issues
- npm.io page: https://npm.io/package/liw-components

## Dependencies (1)

- [ts-keycode-enum](https://npm.io/package/ts-keycode-enum.md) ^1.0.6

## Recent versions

- 2.3.46 (latest) — 2019-02-28
- 2.3.43 — 2019-02-28
- 2.3.42 — 2019-02-28
- 2.3.41 — 2019-01-13
- 2.3.40 — 2019-01-05
- 2.3.39 — 2019-01-05
- 2.3.37 — 2018-11-15
- 2.3.36 — 2018-11-15
- 2.3.35 — 2018-11-15
- 2.3.34 — 2018-11-15
- 2.3.33 — 2018-11-15
- 2.3.32 — 2018-11-15
- 2.3.31 — 2018-11-15
- 2.3.29 — 2018-11-15
- 2.3.28 — 2018-11-15
- … 44 more at https://npm.io/package/liw-components/versions

## README

# Contributing [ru](README.ru.md)

## To fork or not to fork

If you want to change a simple thing, for example, fix a typo or update copy, feel free to use the GitHub web interface, that's perfect. Under the hood, it will do complex things but you don't need to think about it!

## Style

For formatting and code style, we use [Prettier](https://prettier.io/) and [ESLint](https://eslint.org/). It is running automatically before commit:

## Commit convention

Your commit messages should conform to the [Angular convention](https://github.com/conventional-changelog/conventional-changelog/blob/master/packages/conventional-changelog-angular/README.md).

To help you follow this convention, this project is using [commitizen](https://github.com/commitizen/cz-cli). To use it:

1. run `git add` first to add your changes to Git staging area
2. use `npm run commit` to commit

Note: it's not mandatory to always commit with this tool (we don't), but it's great to get introduced to the commit conventions.

## Git guidelines

We do aim having a clean Git history! When submitting a Pull Request, make sure:

- each commit make sense and have a self-explaining message
- there is no unnecessary commits (such as "typo", "fix", "fix again", "eslint", "eslint again" or merge commits)

Some tips to keep a clean Git history while working on your feature branch:

- always update from master with `git pull --rebase origin master` or similar
- you might have to `git push origin --force`, that's all right if you're the only one working on the feature branch
- `git commit --amend` to modify your last commit with "fix", "typo", "prettier" or "eslint" modifications
- `git rebase --interactive` to rewrite the history

We understand Git is not always easy for everyone and want to be inclusive. If it's difficult for you to submit a Pull request with a clean Git history, that's all right, we can always [squash and merge](https://help.github.com/articles/about-pull-request-merges/#squash-and-merge-your-pull-request-commits) it.

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