open-index/open-npm huggingface dataset:
npm package: @relekang/caretaker
Description: A tiny script written in reason that will send you nice notifications like:
Latest version: 0.3.4

# caretaker

A tiny script written in reason that will send you nice notifications like:

![Drink some water 💧](screenshot.png)

## Usage

```shell
npm install -g @relekang/caretaker
caretaker # to run it
# or run in the background
caretaker > /dev/null &
```

Options:
* `--standing-desk` - Will add the message stand for a bit every once in a while.
* `--fast` - Fast mode for development turns minutes into 100ms

## Development

```shell
yarn
yarn build # or yarn watch
```
npm package: @relekang/cli-editor
Description:  An wrapper around the default terminal editor that can edit any object.
Author: Rolf Erik Lekang
Latest version: 1.1.1

# cli-editor

This is a simple editor that can be used to edit javascript objects with the current
editor in the terminal. The editor is fetched with `EDITOR` environment variable.

## Installation

```shell
npm install @relekang/cli-editor
```
or
```shell
yarn add @relekang/cli-editor
```

## Usage

```
import {edit} from "@relekang/cli-editor"

edit({
    fetch: async function() { return getItem() },
    save: async function(item) { return saveItem(item) },
    errorHandler: function (error) {
        return {retry: true, message: "Could not save due to " + error.toString()}
    },
})
.catch(error => console.error("ooops", error))
```
npm package: @relekang/group-by-date
Description: CLI to group files in current directory into date based sub-directory
Author: Rolf Erik Lekang
Latest version: 1.0.0

# group-by-date

Group files by date, will move all files in the current folder
to sub folders with one of the following patterns.

```
$ npm install -g @relekang/group-by-date

$ group-by-date
  Usage: group-by-date [options] [command]

  Commands:
    help     Display help
    version  Display version

  Options:
    -d, --days       Instead of <year>/<file> <year>/<month>/<days>/<file>
    -D, --dry-run    Print instead of doing
    -h, --help       Output usage information
    -m, --months     Instead of <year>/<file> <year>/<month>/<file>
    -o, --one-level  Put month/day in folder-name instead of subfolders when used with --months or --days
    -v, --version    Output the version number
```
npm package: @relekang/ossus-client
Description: An ossus-client
Author: Rolf Erik Lekang
Latest version: 0.2.0

# ossus-client

[last-build]: https://ci.frigg.io/relekang/ossus-client/last/
[build-badge]: https://ci.frigg.io/relekang/ossus-client.svg
[coverage-badge]: https://ci.frigg.io/relekang/ossus-client/coverage.svg
npm package: @relekang/steering
Description: Lint touched code stricter
Author: Rolf Erik Lekang
Latest version: 1.0.9

# steering

Only show style errors of things that have changed since master. This support tools that support exporting output in checkstyle format. This can be useful if you want to convert a project gradually towards a new config, (e.g. adding a new rule from the latest release of your linter). Another case were this is beneficial is were you do not want to break a build when updating the linter.

[![Build status][build-badge]][build-link] ![Coverage][coverage-badge] [![Trello][trello-badge]][trello-link] [![Join the conversation at gitter][gitter-badge]][gitter-link]

## Installation

```
npm install --save-dev @relekang/steering
```

## Usage
You can use this in two different ways, either by reading files or reading from stdin.

### Reading from files

```
steering checkstyle-report.xml
```

### Reading from stdin

```
cat checkstyle-report.xml | steering

# example usage with eslint
eslint . -f checkstyle | steering
```

## Contributing
Firstly, all contributions is super appreciated :sparkles:

As you may have noticed, this repository has no issues here on Github. There is a [trello board][trello-link] with planned features and such. If you have questions, bug report or feature requests you are encouraged to drop by our [gitter channel][gitter-link] and say hi. If you are comfortable with it bug reports in form of a pull-request with a broken test would be awesome. *Unsure about where the test belong?* Then create a new file in the test folder with your test. *Unsure about how to do create a pr?* You can check out [How to create a Pull Request on GitHub][pr-tutorial-link], a video tutorial by @kentcdodds or drop by the [gitter channel][gitter-link] and ask for help.


[trello-link]: https://trello.com/b/GDc2OC4T/steering
[trello-badge]: https://img.shields.io/badge/trello-board-blue.svg
[build-link]: https://ci.frigg.io/relekang/steering
[build-badge]: https://ci.frigg.io/relekang/steering.svg
[coverage-badge]: https://ci.frigg.io/relekang/steering/coverage.svg
[gitter-link]: https://gitter.im/relekang/steering
[gitter-badge]: https://badges.gitter.im/relekang/steering.svg
[pr-tutorial-link]: https://egghead.io/lessons/javascript-how-to-create-a-pull-request-on-github
npm package: @relekang/todo-gist-backend
Description: Gist based storage backend for @relekang/todo
Author: Rolf Erik Lekang
Latest version: 1.0.4

# @relekang/todo-gist-backend

> Gist based storage backend for @relekang/todo

## Usage

```
npm i -g @relekang/todo-gist-backend
```

Add profile with type `gist`. Example config:

```yaml
profiles:
  default:
    type: gist
    id: the-id
    token: personal-access-token-for-gists
```