open-index/open-npm huggingface dataset:
npm package: @proprioo-devops/semantic-release-config
Description: semantic-release shareable config for Proprioo devops projects
Author: Léo Martinez
Latest version: 2.0.2

# @proprioo-devops/semantic-release-config

[**semantic-release**](https://github.com/semantic-release/semantic-release) shareable config for Proprioo devops projects.

## Plugins

This shareable configuration use the following plugins:

- [`@semantic-release/commit-analyzer`](https://github.com/semantic-release/commit-analyzer)
- [`@semantic-release/release-notes-generator`](https://github.com/semantic-release/release-notes-generator)
- [`@semantic-release/changelog`](https://github.com/semantic-release/changelog)
- [`@semantic-release/gitlab`](https://github.com/semantic-release/gitlab)
- [`@semantic-release/git`](https://github.com/semantic-release/git)

## Install

```bash
npm install --save-dev semantic-release @proprioo-devops/semantic-release-config
```

## Usage

The shareable config can be configured in the [**semantic-release** configuration file](https://github.com/semantic-release/semantic-release/blob/master/docs/usage/configuration.md#configuration):

```json
{
  "extends": "@proprioo-devops/semantic-release-config"
}
```

## Configuration

See each [plugin](#plugins) documentation for required installation and configuration steps.
npm package: @proprioo-devops/semantic-release-config-npm
Description: semantic-release shareable config for Proprioo devops projects with package.json
Author: Léo Martinez
Latest version: 1.2.3

# @proprioo-devops/semantic-release-config-npm

[**semantic-release**](https://github.com/semantic-release/semantic-release) shareable config for Proprioo devops projects with package.json.

## Plugins

This shareable configuration use the following plugins:

- [`@semantic-release/commit-analyzer`](https://github.com/semantic-release/commit-analyzer)
- [`@semantic-release/release-notes-generator`](https://github.com/semantic-release/release-notes-generator)
- [`@semantic-release/changelog`](https://github.com/semantic-release/changelog)
- [`@semantic-release/npm`](https://github.com/semantic-release/npm)
- [`@semantic-release/gitlab`](https://github.com/semantic-release/gitlab)
- [`@semantic-release/git`](https://github.com/semantic-release/git)

## Install

```bash
npm install --save-dev semantic-release @proprioo-devops/semantic-release-config-npm
```

## Usage

The shareable config can be configured in the [**semantic-release** configuration file](https://github.com/semantic-release/semantic-release/blob/master/docs/usage/configuration.md#configuration):

```json
{
  "extends": "@proprioo-devops/semantic-release-config-npm"
}
```

## Configuration

See each [plugin](#plugins) documentation for required installation and configuration steps.
npm package: @proprioo-devops/semantic-release-config-test
Description: semantic-release shareable config for Proprioo devops projects
Author: Léo Martinez
Latest version: 1.0.7

# @proprioo-devops/semantic-release-config

[**semantic-release**](https://github.com/semantic-release/semantic-release) shareable config for Proprioo devops projects.

## Plugins

This shareable configuration use the following plugins:

- [`@semantic-release/commit-analyzer`](https://github.com/semantic-release/commit-analyzer)
- [`@semantic-release/release-notes-generator`](https://github.com/semantic-release/release-notes-generator)
- [`@semantic-release/changelog`](https://github.com/semantic-release/changelog)
- [`@semantic-release/gitlab`](https://github.com/semantic-release/gitlab)
- [`@semantic-release/git`](https://github.com/semantic-release/git)

## Install

```bash
npm install --save-dev semantic-release @proprioo-devops/semantic-release-config
```

## Usage

The shareable config can be configured in the [**semantic-release** configuration file](https://github.com/semantic-release/semantic-release/blob/master/docs/usage/configuration.md#configuration):

```json
{
  "extends": "@proprioo-devops/semantic-release-config"
}
```

## Configuration

See each [plugin](#plugins) documentation for required installation and configuration steps.
npm package: @proprioo/hokkaido
Description: Proprioo typings
Author: Tech Proprioo
Latest version: 14.1.0

# Hokkaido

Hokkaido is our typings / helpers library. Made with ❤️.

## How to build ?

Use `npm run build`

## Update version

Before each change, please update `CHANGELOG.md` with a new version using the following template:

```markdown
**major.minor.patch**

    * Commit message

    OR

    **BREAKING CHANGE** Commit message
```

- Fix: **patch**
- Component / Feature: **minor**
- Everything which can bring changes in the different projects: **major**

When changelog is updated, don't forget to bump the `package.json` version with:

```
$ npm version [major | minor | patch]
```

## Release new version to npm.js

- Publishing is triggered by pushing a tag matching `v*.*.*` (e.g., `v1.2.3`) to the repository.
- The workflow runs build, lint, and tests before publishing.
- Build artifacts are uploaded for traceability.

See [CONTRIBUTING.md](./CONTRIBUTING.md) for more details.

### Status Badge

![Publish workflow](https://github.com/casavo/hokkaido/actions/workflows/publish-npm.yml/badge.svg)
npm package: @props-labs/fuels
Description: Props Minting SDK for managing NFTs on the Fuel network
Author: Props Labs, Calvin Hoenes
Latest version: 0.2.7

# Props SDK

The Props SDK allows anyone to integrate minting NFTs on Fuel with just a few lines of code with a powerful built-in incentive protocol that rewards builders, creators and collectors.

## Documentation

For detailed documentation and API reference, please visit our comprehensive documentation site:

[Props SDK Documentation](https://props-fuels.vercel.app)


## Getting Started

### Installation

To install the SDK, run:

```bash
npm install @props-labs/fuels
```

```bash
pnpm install @props-labs/fuels
```

```bash
yarn add @props-labs/fuels
```

## Usage

To use the SDK, you must first create an instance of the `PropsSDK` class:

```javascript
import { PropsSDK } from '@props/fuels';
import { Provider, Wallet } from 'fuels';

const provider = new Provider('https://testnet.fuel.network');
const wallet = Wallet.fromPrivateKey('your-private-key');

const propsClient = new PropsSDK({
  network: 'testnet',
});

async function createEdition() {
  const edition: Edition = await propsClient.editions.create({
    name:"Edition 1",
    symbol: "ED1",
    metadata: {
      name: "Edition 1",
      description: "First edition",
      image: "image_url",
    },
    options: {
      maxSupply: 100,
      owner: wallet,
    }
  });
  console.log(`Created edition with ID: ${editionId}`);
}

createEdition();
```


## TODO

- [x] Merkle-Based Allowlists
- [x] Flexible Mint Dates
npm package: @propsproject/nft-core
Description: Props NFT core contracts
Author: Props
Latest version: 0.0.11

# Props NFT core

Props NFT issuance core contracts.

### Usage

```bash
# Install dependencies
npm install

# Compile contracts
npm run compile
```

### Testing

There are two types of tests for the contracts: regular tests, which run on a clean state, and forking tests, which use network forking and depend on existing deployed contracts (eg. Gnosis Safe factory). Regular tests can be run via `npm run test` while forking tests can be run via `npm run test:forking`. Forking tests require access to an archive node and need to be run against a specific block number where network forking will take place. These parameters must be specified in the `.env` secrets file as follows:

```bash
INFURA_KEY=
BLOCK_NUMBER=
```

### Deployment

Deployment scripts reside in the `./scripts/deployment/` directory. For example, running `npx hardhat --network NETWORK run ./scripts/deployment/PropsERC721Factory.ts` will run the deployment process for the `PropsERC721Factory` contract. As part of running the deployment script, the deployed addresses, deployment blocks,and ABIs of the deployed contracts will be saved in the `./deployments` folder. Optionally, the deployed contracts can be registered to Biconomy for supporting relaying meta-transactions. The deployment process depends on the following variables, to be added to the `.env` secrets file:

```bash
DEPLOYER_PK=
BICONOMY_AUTH_TOKEN=
BICONOMY_API_KEY=
```

### Publishing

The SDK depends on the latest contract deployments (eg. `./deployments` directory). For this reason, when triggering a new deployment of any contract, make sure to publish the changes via `npm publish` (not before making sure to bump the package version) and then update the SDK to use the latest version. The SDK will automatically pick up the latest available deployment of the contracts. Related, the corresponding subgraph also needs to be updated to the latest deployment.
npm package: @propsproject/nft-sdk
Description: Props NFT SDK
Author: Props
Latest version: 0.0.12

# Props NFT SDK

This SDK provides utility classes for interacting with instances of the Props NFT core contracts.

### Models

The SDK is chain-agnostic and able to connect to any existing deployment of any Props NFT core contract on any network (for now, the SDK is linked to the latest active deployment for the corresponding network, but support for any previous deployments will be added soon). Make sure the provider and signers that get connected to the models are on the right network.

##### [`PropsERC721`](https://github.com/propsproject/nft-monorepo/tree/main/packages/sdk/src/models/PropsERC721)

Available methods:

- `approve`
- `mintAndTransfer`
- `safeTransferFrom`
- `setApprovalForAll`

##### [`PropsERC721Factory`](https://github.com/propsproject/nft-monorepo/tree/main/packages/sdk/src/models/PropsERC721Factory)

Available methods:

- `deploy`

### Transaction modes

The SDK has support for both direct transactions and calldata generation (which can be used for various purposes, eg. to generate meta-transactions for any contract interaction). By default, the model assumes a direct transactions mode, but this can be changed via the `options` parameter each model accepts in the constructor. Calldata encoding can be turned on by turning on the `onlyGenerateCalldata` field. In this case, all SDK action methods will return the encoded calldata corresponding to executing that specific action. This calldata can be used to generate a meta-transaction or a Gnosis Safe transaction.

### Usage

For some usage examples, check out the [`examples`](https://github.com/propsproject/nft-monorepo/tree/main/packages/sdk/src/examples).