open-index/open-npm huggingface dataset:
npm package: @pie-api/semantic-release-jira-releases
Description: [**semantic-release**](https://github.com/semantic-release/semantic-release) plugin to publish a jira release.
Latest version: 0.12.0

# semantic-release-jira-releases

[**semantic-release**](https://github.com/semantic-release/semantic-release) plugin to publish a jira release.

[![Travis](https://img.shields.io/travis/UpHabit/semantic-release-jira-releases.svg)](https://travis-ci.org/UpHabit/semantic-release-jira-releases)

[![npm latest version](https://img.shields.io/npm/v/semantic-release-jira-releases/latest.svg)](https://www.npmjs.com/package/semantic-release-jira-releases)


| Step               | Description                                                                                                                                   |
|--------------------|----------------------------------------------------------------------------|
| `verifyConditions` | Validate the config options and checks for `JIRA_EMAIL` and `JIRA_TOKEN` in the environment |
| `sucess`           | Find all tickets from commits and add them to a new release on JIRA        |

## Install

```bash
$ npm install --save-dev semantic-release-jira-releases
$ yarn add --dev semantic-release-jira-releases
```

### Configuration
The plugin should be added to your config
```json
{
  "plugins": [
    "@semantic-release/commit-analyzer",
    "@semantic-release/release-notes-generator",
    "@semantic-release/git",
    ["semantic-release-jira-releases", {
      "projectId": "1",
      "releaseNameTemplate": "Test v${version}",
      "jiraHost": "uphabit.atlassian.net",
      "ticketPrefixes": [ "TEST", "UH"],
      "ticketRegex": "[a-zA-Z]{3,5}-\\d{3,5}"
    }]
  ]
}

Please note that `ticketRegex` cannot be used together with `ticketPrefixes`.
```
```typescript
interface Config {
  
  /// A domain of a jira instance ie: `uphabit.atlasian.net`
  jiraHost: string;

  // A list of prefixes to match when looking for tickets in commits. Cannot be used together with ticketRegex.
  // ie. ['TEST'] would match `TEST-123` and `TEST-456`
  ticketPrefixes?: string[];

  // A unescaped regex to match tickets in commits (without slashes). Cannot be used together with ticketPrefixes.
  // ie. [a-zA-Z]{4}-\d{3,5} would match any ticket with 3 letters a dash and 3 to 5 numbers, such as `TEST-456`, `TEST-5643` and `TEST-56432`
  ticketRegex?: string;
  
  // The id for the project releases will be created in
  projectId: number;
  
  // A lodash template with a single `version` variable
  // defaults to `v${version}` which results in a version that is named like `v1.0.0`
  // ex: `Semantic Release v${version}` results in `Semantic Release v1.0.0`
  releaseNameTemplate?: string;

  // The number of maximum parallel network calls, default 10
  networkConcurrency?: number;

  // indicates if a new release created in jira should be set as released
  released?: boolean;

  // include the release date when creating a release in jira
  releaseDate?: boolean;
}
```
npm package: @pie-cli-libs/installer
Description: installer for pie elements
Latest version: 1.5.4

# installer

For installing dependencies of a [pie][p] item.

## build

```shell
npm run build
```

## test
```shell
npm test # unit tests
npm run integration-test # this is disabled for now. instead run: 
./node_modules/.bin/jest --config jest.config.int.js
```

## publish

See the main readme.


## Item Configuration

A pie item will have the following configuration: 

```javascript
{
  /** 
    * elements is a mapping between a custom element name and it's package.
    * on the left side is the name of the custom element that'll be used.
    * on the right side is the npm style dependency look up.
    * > NOTE: The npm package name does not need to match the element name, they'll be associated with each other.
    */

  elements: {
    'el-one': '../..', //where ../.. is an npm package called located 2 directories above
    'el-two': '^1.0.0', //looks for an npm package called 'el-two'
    'el-three': '@scope/name@^2.0.1' //looks for an npm package '@scope/name@^2.0.1`
    'el-four': 'user/repo#v2.0.0' // github repo
  },
  models: [
    { id: '1', element: 'el-one', ...}
  ]
}
```

Using the above [pie][p] `item` definition, `install` will install the dependencies needed and will return information on the installation.

The installation directory will look like so: 

```shell
root
├── .configure   
│   ├── node_modules # configure dependencies in here
│   └── package.json
├── .controllers
│   ├── node_modules # controller dependencies in here
│   └── package.json
├── node_modules # player dependencies in here
└── package.json
```

It'll return an array of objects similar to: 
```javascript
{
  "element": "text-entry",
  "isLocal": true,
  "isPackage": true,
  "main": {
    "dir": "/Users/edeustace/dev/github/PieElements/pie-elements/packages/text-entry/docs/demo/.pie",
    "moduleId": "@pie-elements/text-entry",
    "tag": "text-entry"
  },
  "src": "../..",
  "controller": {
    "dir": "/Users/edeustace/dev/github/PieElements/pie-elements/packages/text-entry/docs/demo/.pie/.controller",
    "moduleId": "@pie-elements/text-entry-controller"
  },
  "configure": {
    "dir": "/Users/edeustace/dev/github/PieElements/pie-elements/packages/text-entry/docs/demo/.pie/.configurue",
    "moduleId": "@pie-elements/text-entry-configure",
    "tag": "text-entry-configure"
  }
}
```

[p]: http://pie-framework.org
npm package: @pie-dao/abis
Description: PieDAO's set of frequently used abis in js format.
Author: Dan Matthews
Latest version: 1.0.0

# @pie-dao/abis

## Installation

`yarn add @pie-dao/abis`

## Commands

### yarn lint

Runs the linter to make sure all is well with the world. Please make sure to do this prior to
submitting any PRs. Code which fails linting will be rejected.

### yarn release

Lints and the publishes the to npmjs.org.

## Development

https://reactjs.org/warnings/invalid-hook-call-warning.html#duplicate-react

Note: When developing locally using yarn link, make sure to link react as well:

```
This problem can also come up when you use npm link or an equivalent. In that case, your bundler might “see” two Reacts — one in application folder and one in your library folder. Assuming myapp and mylib are sibling folders, one possible fix is to run npm link ../myapp/node_modules/react from mylib. This should make the library use the application’s React copy.
```
npm package: @pie-dao/blockchain
Description: An extension for PieDAO's eth wrapper. Tracks and locally caches transactions.
Author: Dan Matthews
Latest version: 1.1.1

# @pie-dao/blockchain

## Installation

`yarn add @pie-dao/blockchain`

## Commands

### yarn lint

Runs the linter to make sure all is well with the world. Please make sure to do this prior to
submitting any PRs. Code which fails linting will be rejected.

### yarn release

Lints and the publishes the to npmjs.org.
npm package: @pie-dao/eth
Description: PieDAO's eth wrapper. Provides connection and wallet state management.
Author: Dan Matthews
Latest version: 1.2.0

# @pie-dao/eth

## Installation

`yarn add @pie-dao/eth`

## Commands

### yarn lint

Runs the linter to make sure all is well with the world. Please make sure to do this prior to
submitting any PRs. Code which fails linting will be rejected.

### yarn release

Lints and the publishes the to npmjs.org.

## Development

https://reactjs.org/warnings/invalid-hook-call-warning.html#duplicate-react

Note: When developing locally using yarn link, make sure to link react as well:

```
This problem can also come up when you use npm link or an equivalent. In that case, your bundler might “see” two Reacts — one in application folder and one in your library folder. Assuming myapp and mylib are sibling folders, one possible fix is to run npm link ../myapp/node_modules/react from mylib. This should make the library use the application’s React copy.
```
npm package: @pie-dao/eth-tailwind
Description: PieDAO's eth wrapper tailwind plugin.
Author: Dan Matthews
Latest version: 1.0.0

# @pie-dao/eth-tailwind

## Installation

`yarn add @pie-dao/eth-tailwind`

```
/* tailwind.config.js */
const eth = require('@pie-dao/eth-tailwind');
const piedao = require('@pie-dao/tailwind');

module.exports = {
  theme: {},
  variants: {},
  plugins: [piedao, eth],
}
```

## Commands

### yarn lint

Runs the linter to make sure all is well with the world. Please make sure to do this prior to
submitting any PRs. Code which fails linting will be rejected.

### yarn release

Lints and the publishes the to npmjs.org.

## Development

https://reactjs.org/warnings/invalid-hook-call-warning.html#duplicate-react

Note: When developing locally using yarn link, make sure to link react as well:

```
This problem can also come up when you use npm link or an equivalent. In that case, your bundler might “see” two Reacts — one in application folder and one in your library folder. Assuming myapp and mylib are sibling folders, one possible fix is to run npm link ../myapp/node_modules/react from mylib. This should make the library use the application’s React copy.
```
npm package: @pie-dao/if-unless
Description: Provides two components, If and Unless, for conditional rendering.
Author: Dan Matthews
Latest version: 1.0.1

# @pie-dao/if-unless

## Installation

`yarn add @pie-dao/if-unless`

## Commands

### yarn lint

Runs the linter to make sure all is well with the world. Please make sure to do this prior to
submitting any PRs. Code which fails linting will be rejected.

### yarn release

Lints and the publishes the to npmjs.org.
npm package: @pie-dao/mint
Description: PieDAO's minter components.
Author: Dan Matthews
Latest version: 1.1.1

# @pie-dao/mint

## Installation

`yarn add @pie-dao/mint`

## Commands

### yarn lint

Runs the linter to make sure all is well with the world. Please make sure to do this prior to
submitting any PRs. Code which fails linting will be rejected.

### yarn release

Lints and the publishes the to npmjs.org.

## Development

https://reactjs.org/warnings/invalid-hook-call-warning.html#duplicate-react

Note: When developing locally using yarn link, make sure to link react as well:

```
This problem can also come up when you use npm link or an equivalent. In that case, your bundler might “see” two Reacts — one in application folder and one in your library folder. Assuming myapp and mylib are sibling folders, one possible fix is to run npm link ../myapp/node_modules/react from mylib. This should make the library use the application’s React copy.
```
npm package: @pie-dao/mint-tailwind
Description: PieDAO's minting package tailwind plugin.
Author: Dan Matthews
Latest version: 1.0.0

# @pie-dao/mint-tailwind

## Installation

`yarn add @pie-dao/mint-tailwind`

```
/* tailwind.config.js */
const eth = require('@pie-dao/eth-tailwind');
const mint = require('@pie-dao/mint-tailwind');
const piedao = require('@pie-dao/tailwind');

module.exports = {
  theme: {},
  variants: {},
  plugins: [piedao, eth, mint],
}
```

## Commands

### yarn lint

Runs the linter to make sure all is well with the world. Please make sure to do this prior to
submitting any PRs. Code which fails linting will be rejected.

### yarn release

Lints and the publishes the to npmjs.org.

## Development

https://reactjs.org/warnings/invalid-hook-call-warning.html#duplicate-react

Note: When developing locally using yarn link, make sure to link react as well:

```
This problem can also come up when you use npm link or an equivalent. In that case, your bundler might “see” two Reacts — one in application folder and one in your library folder. Assuming myapp and mylib are sibling folders, one possible fix is to run npm link ../myapp/node_modules/react from mylib. This should make the library use the application’s React copy.
```
npm package: @pie-dao/proxy
Description: Generic proxy pattern which can be used with any smart contract.
Author: Pie DAO
Latest version: 1.0.0

# Pie Proxy

Generic proxy pattern which can be used with any smart contract.

This project uses [Buidler](https://buidler.dev) and [Ethers](https://docs.ethers.io/ethers.js/html/index.html).

# 🚨Reserved Storage Slots 🚨

Using these slots in the implementation by accident would be an issue.
```
bytes32 constant IMPLEMENTATION_SLOT = keccak256(abi.encodePacked("IMPLEMENTATION_SLOT"));
bytes32 constant OWNER_SLOT = keccak256(abi.encodePacked("OWNER_SLOT"));
bytes32 constant PAUSED_SLOT = keccak256(abi.encodePacked("PAUSED_SLOT"));
bytes32 constant PAUZER_SLOT = keccak256(abi.encodePacked("PAUZER_SLOT"));
```

## Features 

### Upgradeability

The proxy owner can update the implementation and the overrides contract

### Pauzing

Allows the pauser address to pause the contract in case of emergency

## Installing dependencies

Clone this repository, then install the dependencies with `yarn`.

## Available Functionality

### Build Contracts

`yarn compile`

### Generate TypeChain Typings

`yarn build`

### Run Contract Tests

`yarn test`

### Run Coverage Report for Tests

`yarn coverage`


### Deploy to Ethereum

Modify network config in `buidler.config.ts` and add API key and private key, then run:

`npx buidler run --network rinkeby scripts/deploy.ts`

### Verify on Etherscan

Add Etherscan API key to `buidler.config.ts`, then run:

`npx buidler verify-contract --contract-name Counter --address <DEPLOYED ADDRESS>`
npm package: @pie-dao/tailwind
Description: PieDAO tailwindcss plugin for providing all default styles and classes.
Author: Dan Matthews
Latest version: 1.1.2

# @pie-dao/tailwind

This package provides the [tailwindcss](https://tailwindcss.com) plugin used by the PieDAO [frontend-template repo](https://github.com/pie-dao/frontend-template). Including it in your tailwindcss configuration will give you all of the base styles and classes discussed in the [styling section of https://docs.piedao.org](https://docs.piedao.org/development-resources/styling).

## Installation

`yarn add @pie-dao/tailwind`

```
/* tailwind.config.js */
const piedao = require('@pie-dao/tailwind');

module.exports = {
  theme: {},
  variants: {},
  plugins: [piedao],
}
```

## Commands

### yarn lint

Runs the linter to make sure all is well with the world. Please make sure to do this prior to
submitting any PRs. Code which fails linting will be rejected.

### yarn release

Lints and the publishes the to npmjs.org.
npm package: @pie-dao/utils
Description: PieDAO's common utility functions.
Author: Dan Matthews
Latest version: 1.0.0

# @pie-dao/utils

## Installation

`yarn add @pie-dao/utils`

## Commands

### yarn lint

Runs the linter to make sure all is well with the world. Please make sure to do this prior to
submitting any PRs. Code which fails linting will be rejected.

### yarn release

Lints and the publishes the to npmjs.org.