open-index/open-npm huggingface dataset:
npm package: @hmp-global/hmp-dev-tools
Description: Development tool suite with configuration files.
Author: John Kaeser
Latest version: 1.0.1

# HMP Dev Tools

A collection of predefined dev tool dependencies and their respective configuration files.

## Task
https://taskfile.dev/

### Usage
Assuming you are using the standard DDEV setup:

1. Create a `Taskfile.yml` at the root of your project.
2. Add the following:
    ```yml
    includes:
      hmp-dev-tools:
        taskfile: ./node_modules/@hmp-global/hmp-dev-tools/configs/Taskfile.yml
        optional: true
        flatten: true
    ```
3. Run `ddev task -a` and verify this package's tasks appear in the list.

## ESLint
https://eslint.org/

8.x is outdated, but we use it because that's what Drupal core uses. See https://github.com/drupal/drupal/blob/main/core/package.json.

### Usage
```bash
ln -s ./node_modules/@hmp-global/hmp-dev-tools/configs/.eslintrc.json .eslintrc.json
```

## Stylelint
https://stylelint.io/

### Usage
```bash
ln -s ./node_modules/@hmp-global/hmp-dev-tools/configs/stylelint.config.mjs stylelint.config.mjs
```
npm package: @hmphu/capacitor-isdebug
Description: Detect if app is run in debug or release mode
Author: guilherme-tc
Latest version: 1.0.5

# capacitor-isdebug

Detect if app is run in debug or release mode

## Install

```bash
npm install @guimapkx/capacitor-isdebug
npx cap sync
```

## API

<docgen-index>

* [`getIsDebug()`](#getisdebug)

</docgen-index>

<docgen-api>
<!--Update the source file JSDoc comments and rerun docgen to update the docs below-->

### getIsDebug()

```typescript
getIsDebug() => Promise<{ value: boolean | null; }>
```

Return if app is run on debug or release mode.
Return null if can't detect.

**Returns:** <code>Promise&lt;{ value: boolean | null; }&gt;</code>

--------------------

</docgen-api>
npm package: @hmps/create-release
Description: Git flow release creator ===
Author: Hampus Persson
Latest version: 0.1.1

Git flow release creator
===

A small and simple Node CLI tool to create a new release branch, following the [git-flow workflow](http://nvie.com/posts/a-successful-git-branching-model/).

## Installation

Clone this repo and run `npm link` in the root folder.

This will create two CLI commands:

- `create-release`
- `cr`

They both do the same thing, `cr` is just a shorter version.

## Usage

`$ create-release [major|minor|patch]`

If no release type is specified, a patch bump is performed.

Git flow release creator assumes that you can run `git-flow` commands from your CLI.

## License
MIT
npm package: @hmps/pj
Description: A CLI tool that reads and reports what's in package.json
Author: Hampus Persson
Latest version: 0.1.0

PEE-JAY
=======

PJ is a easy to use CLI tool to read `package.json` files. It sprung out of my own work where I often find myself looking for what version a package is, what dependency ranges are defined, what the main file is etc.

# Usage

`$ pj` will print out the entire package.json.
`$ pj [pattern]` will find property keys in package.json that matches the given pattern. E.g. "v" will find and print "version" and any other keys starting with "v".

# License
MIT (c) [Hampus Persson](http://hmps.se)
npm package: @hmps/what-version
Description: What version ===
Author: Hampus Persson
Latest version: 0.1.0

What version
===

A small and simple Node CLI tool to inspect the specified version in a package's package.json.

## Installation

`npm install -g @hmps/what-version`

This will create two CLI commands:

- `what-version`
- `wv`

They both do the same thing, `wv` is just a shorter alternative.

## Usage

`$ what-version` or `$ wv`

## License
MIT