open-index/open-npm huggingface dataset:
npm package: @healthmatch/jira-prepare-commit-msg
Description: Husky Git hook to add JIRA ticket ID into the commit message
Author: Dmitry Shilov
Latest version: 1.3.4

# jira-prepare-commit-msg

The husky command to add JIRA ticket ID into the commit message if it is missed.

The JIRA ticket ID is taken from a git branch name.

## Installation

Install the package using NPM

```bash
npm install husky jira-prepare-commit-msg --save-dev
```

Inside your package.json add a standard husky npm script for the git hook:

```json
{
  "husky": {
    "hooks": {
      "prepare-commit-msg": "jira-prepare-commit-msg"
    }
  }
}
```

## Configuration

Starting with v1.3 you can now use different ways of configuring it:

* `jira-prepare-commit-msg` object in your `package.json`
* `.jirapreparecommitmsgrc` file in JSON or YML format
* `jira-prepare-commit-msg.config.js` file in JS format

See [cosmiconfig](https://github.com/davidtheclark/cosmiconfig) for more details on what formats are supported.

#### `package.json` example:

```json
{
  "jira-prepare-commit-msg": {
    "messagePattern": "[$J]\n$M",
    "jiraTicketPattern": "([A-Z]+-\\d+)",
    "commentChar": "#",
    "isConventionalCommit": false
  }
}
```

#### Supported message pattern

`jira-prepare-commit-msg` supports special message pattern to configure where JIRA ticket number will be inserted. 
* Symbols `$J` will be replaced on JIRA ticket number
* Symbols `$M` will be replaced on commit message.
 
Pattern `[$J]\n$M` is currently supported by default. 

```json
{
  "jira-prepare-commit-msg": {
    "messagePattern": "[$J]\n$M"
  }
}
```

##### Examples

* `[$J] $M`
* `[$J]-$M`
* `$J $M`

**NOTE:** the supplied commit message will be cleaned up by `strip` mode.

#### Supported JIRA ticket pattern

`jira-prepare-commit-msg` allows using custom regexp string pattern to search JIRA ticket number.

Pattern `([A-Z]+-\\d+)` is currently supported by default. 

**NOTE:** to search JIRA ticket pattern flag `i` is used: `new RegExp(pattern, i')`  

```json
{
  "jira-prepare-commit-msg": {
    "jiraTicketPattern": "([A-Z]+-\\d+)"
  }
}
```

#### Git comment char

Git uses `#` by default to comment lines in the commit message. If default char was changed `jira-prepare-commit-msg` can allow set it.

```json
{
  "jira-prepare-commit-msg": {
    "commentChar": "#"
  }
}
```

#### Conventional commit

`jira-prepare-commit-msg` supports [conventional commit](https://www.conventionalcommits.org). To insert JIRA
ticket number to the description set the following setting:

```json
{
  "jira-prepare-commit-msg": {
    "isConventionalCommit": false
  }
}
```

**NOTE:** For description will be applied `messagePattern`

##### Examples

If the configuration is:

```json
{
  "jira-prepare-commit-msg": {
    "messagePattern": "[$J] $M",
    "isConventionalCommit": false
  }
}
``` 

and commit message is `fix(test)!: important changes` then at result will be `fix(test)!: [JIRA-1234] important changes`

## TODO

- [x] Support user patterns
- [x] Support configuration (package.json)
- [x] Lint
- [x] Tests
  - [ ] Test for configuration

## License

MIT
npm package: @healthnz/pattern-library-themes
Description: Health NZ - Design Pattern Library. Generate multi platform design tokens using Style Dictionary
Author: Kyle Beattie
Latest version: 1.0.0

# Pattern library themes

`@healthnz/pattern-library-themes`

### Configuration

[Style Dictionary](https://amzn.github.io/style-dictionary/) can output design tokens for multiple platforms from a single source.

Add your platform to `config.js`.
For example, a web platform with a built in format and a custom format:

```json
"platforms": {
  "web": {
    "transformGroup": "js",
    "files": [
      {
        "format": "javascript/es6",
        "destination": "theme.ts"
      },
      {
        "format": "myCustomFormat",
        "destination": "myCustomFormat.ts"
      },
    ]
  }
}
```

#### Custom formats

Create a file for your platform (e.g `ios.js`) in `scripts/formats`.
```js
const registerFormats = (StyleDictionary) => {
  StyleDictionary.registerFormat({
    name: 'ios/swift-custom-formatter',
    formatter: function ({ options }) {
      return `
        
      `;
    }
  });
  
  // Register more formats here
};

export default registerFormats;
```

Add the formatter to the platform's `files` array in `config.js`:

```json
"platforms": {
  "files": [
    {
      "format": "ios/swift-custom-formatter",
      "destination": "MyCustomFormat.swift"
    }
  ]
}
```

---

### Usage

1. Export tokens from Figma using the [Design tokens plugin](https://github.com/lukasoppermann/design-tokens).

2. Place the exported `.json` file(s) into `input/themes/[themeName]`.

3. Commit the changes, and GitLab CI will:
   - Run Style Dictionary transforms on the tokens.
   - Publish a new release of the package to NPM. 

Once published, the updated theme will be available in the next version.

#### JavaScript (Vanilla Extract)
```js
import { myTheme } from '@healthnz/pattern-library-themes';

...

<ThemeProvider theme={myTheme}>
  ...
</ThemeProvider>
```
npm package: @healthscreening/sequelize-lazy-migrations
Description: Sequelize migrations generator & runner
Author: Michael Maslov
Latest version: 2.0.0
Deprecated: Repository has been archived and package is no longer maintained.

# sequelize-lazy-migrations

Migration generator & runner for sequelize

This package provide two tools:
* `makemigration` - tool for create new migrations
* `runmigration` - tool for apply created by first tool migrations

## Install
`npm install @healthscreening/sequelize-lazy-migrations`

## Usage
* Init sequelize, with sequelize-cli, using `sequelize init`
* Create your models
* Create initial migration - run:

`makemigration --name <migration name>`
* Change models and run it again, model difference will be saved to the next migration

To preview new migration, without any changes, you can run:

`makemigration --preview`

`makemigration` tool creates `_current.json` file in `migrations` dir, that is used to calculate difference to the next migration. Do not remove it!

To create and then execute migration, use:
`makemigration --name <name> -x`

## Executing migrations
* There is simple command to perform all created migrations (from selected revision):

`runmigration`
* To select a revision, use `--rev <x>`
* If migration fails, you can continue, use `--pos <x>`
* To prevent execution next migrations, use `--one`


For more information, use `makemigration --help`, `runmigration --help`

## TODO:

* Unit tests
* Migration action sorting procedure need some fixes. When many foreign keys in tables, there is a bug with action order. Now, please check it manually (`--preview` option)
* Need to check (and maybe fix) field types: `BLOB`, `RANGE`, `ARRAY`, `GEOMETRY`, `GEOGRAPHY`
* Downgrade is not supported, add it
* This module tested with postgresql (I use it with my projects). Test with mysql and sqlite.
npm package: @healthwise-ui/core
Description: Shared React UI library that implements the Healthwise design language.
Author: Healthwise
Latest version: 3.3.0

# Healthwise UI

Healthwise UI is a library of shared React components that you can use to quickly build an app using the Healthwise design language.

![GitHub](https://img.shields.io/github/license/healthwise/healthwise-ui?style=flat-square)
![npm (scoped)](https://img.shields.io/npm/v/@healthwise-ui/core?style=flat-square)
![npm bundle size (scoped)](https://img.shields.io/bundlephobia/minzip/@healthwise-ui/core?style=flat-square)

- [Healthwise UI](#healthwise-ui)
  - [Installation](#installation)
  - [Usage](#usage)
  - [Running Tests](#running-tests)
  - [Documentation](#documentation)
  - [Contributing](#contributing)
  - [License](#license)

## Installation

Install @healthwise-ui/core with npm

```bash
  npm install @healthwise-ui/core
```

## Usage

```jsx
import { Button, ProfileIcon } from '@healtwise-ui/core'

function App() {
  return (
    <Button color="primaryDark" raised>
      <ProfileIcon /> Profile
    </Button>
  )
}
```

## Running Tests

To run tests, run the following command

```bash
  npm run test
```

## Documentation

[Documentation](https://healthwise.github.io/healthwise-ui/)

In order to enable husky Git hooks manually run the following from the root directory:

```
npx --no-install husky install
```

More info about this bug at the link [here](https://github.com/typicode/husky/issues/851).

## Contributing

Contributions are always welcome!

See `CONTRIBUTING.md` for ways to get started.

## License

[MIT](https://choosealicense.com/licenses/mit/)
npm package: @healx/react-day-picker
Description: Flexible date picker component for React
Author: Giampaolo Bellavite
Latest version: 7.1.12

<p align="center">
<a href="http://react-day-picker.js.org"><img width="80" style="margin: 0 auto" alt="title" src="https://user-images.githubusercontent.com/120693/33364057-0d4a962a-d4e3-11e7-8506-0f9aede2b345.png"></a>
</p>
<h1 align="center">react-day-picker</h1>
<p align="center">
  Flexible date picker component for <a href="https://facebook.github.io/react/">React</a>.
  <br />
  Highly customizable, localizable, with ARIA support, no external dependencies, 9KB gzipped
</p>
<p align="center">
  <a href="http://react-day-picker.js.org"><img width="266" alt="screen shot 2017-11-29 at 08 53 17" src="https://user-images.githubusercontent.com/120693/33363979-cb60fb5a-d4e2-11e7-8d21-f4779b8b9105.png">
</a>
</p>
<p align="center">
  <a href="http://react-day-picker.js.org">Documentation</a> | <a href="http://react-day-picker.js.org/examples/basic">Examples</a> | <a href="http://react-day-picker.js.org/api/DayPicker">API</a> | <a href="http://react-day-picker.js.org/changelog">Changelog</a>
</p>
<p align="center">
  <a href="https://www.npmjs.com/package/react-day-picker">
    <img src="https://img.shields.io/npm/v/react-day-picker.svg?style=flat-square" alt="npm version">
  </a>
  <a href="http://npm-stat.com/charts.html?package=react-day-picker">
    <img src="https://img.shields.io/npm/dm/react-day-picker.svg?style=flat-square" alt="npm downloads">
  </a>
  <a href="https://circleci.com/gh/gpbl/react-day-picker">
    <img src="https://img.shields.io/circleci/project/github/gpbl/react-day-picker/master.svg?style=flat-square" alt="circleci">
  </a>
  <a href="https://codecov.io/gh/gpbl/react-day-picker">
    <img src="https://img.shields.io/codecov/c/github/gpbl/react-day-picker/master.svg?style=flat-square" alt="npm downloads">
  </a>
</p>

## Get support

Please fork and use [https://codesandbox.io/s/XDAE3x0W8](https://codesandbox.io/s/XDAE3x0W8) to reproduce your problem.

* Ask on on [Stack Overflow](http://stackoverflow.com/questions/tagged/react-day-picker?sort=newest) tagging your question with `react-day-picker`.
* Open a [new issue](https://github.com/gpbl/react-day-picker/issues/new) on GitHub.
* Join the [Gitter room](https://gitter.im/gpbl/react-day-picker) to chat with other developers.