open-index/open-npm huggingface dataset:
npm package: @nitish002/pricing-plan-ui
Description: A reusable React pricing plan UI component built with Tailwind CSS
Author: Nitish Sharma
Latest version: 1.0.4



📦 Pricing Plan UI — React + Tailwind Component

A fully customizable and reusable Pricing Plan UI component built with React, TypeScript, TailwindCSS, and Lucide icons.
Perfect for integrating beautiful pricing sections into any React project with minimal setup.

🚀 Installation
npm install pricing-plan-ui
# or
yarn add pricing-plan-ui


🧠 Note: This package requires your project to have TailwindCSS and React 18+ already configured.

🧩 Usage
Import and use in your project:
import React from "react";
import { Pricing } from "pricing-plan-ui";

const plans = [
  {
    name: "Starter",
    price: "$29",
    period: "/month",
    description: "Perfect for individuals and small teams",
    features: ["5 campaigns", "10,000 emails/month", "Basic analytics"],
  },
  {
    name: "Pro",
    price: "$79",
    period: "/month",
    description: "Ideal for growing businesses",
    features: ["Unlimited campaigns", "Advanced analytics", "Priority support"],
    popular: true,
  },
  {
    name: "Enterprise",
    price: "$199",
    period: "/month",
    description: "For large organizations with advanced needs",
    features: ["Dedicated manager", "Custom integrations", "Unlimited users"],
  },
];

function App() {
  return (
    <Pricing
      title="Flexible Plans for Every Team"
      subtitle="Choose the plan that best suits your needs"
      plans={plans}
      accentColor="from-indigo-600 to-pink-600"
      ctaTitle="Ready to get started?"
      ctaSubtitle="Start your free trial today — no credit card required"
      ctaButton="Start Free Trial"
    />
  );
}

export default App;

⚙️ Props Reference
Prop Name	Type	Default Value	Description
title	string	"Simple, Transparent Pricing"	Main heading text shown at the top.
subtitle	string	"Choose the perfect plan for your needs."	Subtext shown below the title.
plans	Plan[] (required)	—	Array of plan objects (see below).
accentColor	string	"from-blue-600 to-purple-600"	Tailwind gradient color used for highlights.
ctaTitle	string	"Ready to get started?"	CTA (call-to-action) section heading.
ctaSubtitle	string	"Join thousands of users using our platform."	CTA subtext.
ctaButton	string	"Start Free Trial"	CTA button text.
🧱 Plan Object Structure

Each plan in the plans array should follow this interface:

interface Plan {
  name: string;          // Plan name (e.g., Starter)
  price: string;         // Plan price (e.g., $29)
  period?: string;       // Optional billing period (e.g., /month)
  description: string;   // Short plan description
  features: string[];    // List of features
  popular?: boolean;     // Highlight this plan as "Most Popular"
}

🎨 Customization Examples
Change Accent Colors

You can customize the gradient theme with Tailwind classes:

<Pricing accentColor="from-green-500 to-emerald-700" />

Add Your Own CTA Text
<Pricing
  ctaTitle="Launch your first campaign today!"
  ctaSubtitle="No setup fees, cancel anytime"
  ctaButton="Get Started"
/>
npm package: @nitishxyz/solar
Description: A powerful CLI tool for Solana developers that simplifies common development tasks
Author: nitishxyz
Latest version: 0.1.14

# Solar CLI

A powerful command-line interface tool for Solana developers that simplifies common development tasks.

<img src="./assets/solar.gif" alt="Solar CLI Demo" width="800"/>

## Features

- 🔑 Generate and manage Solana keypairs
- 💫 Request SOL airdrops for development
- ⚙️ Flexible configuration management (global & local)
- 🔄 Sync settings with Solana CLI
- 💻 Interactive mode for easier usage
- 🌐 Support for multiple networks (localnet, devnet, testnet, mainnet)

## Development

### Prerequisites

- [Bun](https://bun.sh) v1.1.42 or higher
- Node.js 18 or higher

### Setup

1. Clone the repository:

```bash
git clone https://github.com/nitishxyz/solar.git
cd solar
```

2. Install dependencies:

```bash
bun install
```

3. Run in development mode:

```bash
bun run cli.ts
```

### Building

Build the project:

```bash
bun run build
```

The built files will be in the `dist` directory.

### Installation

#### From NPM

```bash
npm install -g @nitishxyz/solar
```

#### From Source

```bash
npm install -g .
```

## Usage

### Interactive Mode

Start the interactive CLI interface:

```bash
solar
# or
solar -i
```

### Command Mode

```bash
solar <command> [options]
```

### Available Commands

#### Configuration

```bash
solar config [options] [network]
  -g, --global    Use global configuration
  -l, --local     Use local configuration (default)
  -s, --show      Show current configuration
  -i, --init      Initialize configuration file
  -k, --keypair   <path> Set keypair path
```

#### Keypair Management

```bash
solar keygen [options]
  -g, --global    Save to global keypair location

solar keyinfo <file>
  View keypair information
```

#### Airdrop

```bash
solar airdrop <address>
  Request 1 SOL airdrop for development
```

#### Sync with Solana CLI

```bash
solar sync
  Sync configuration with Solana CLI
```

## Configuration

Solar CLI supports both global and local configuration:

- Global config: `~/.config/solar/config.json`
- Local config: `./solar-config.json` (in project directory)

Local configuration takes precedence over global configuration.

### Supported Networks

- `localnet`: http://127.0.0.1:8899
- `devnet`: https://api.devnet.solana.com
- `testnet`: https://api.testnet.solana.com
- `mainnet`: https://api.mainnet-beta.solana.com
- Custom RPC URL

## Contributing

1. Fork the repository
2. Create your feature branch (`git checkout -b feature/amazing-feature`)
3. Commit your changes (`git commit -m 'Add some amazing feature'`)
4. Push to the branch (`git push origin feature/amazing-feature`)
5. Open a Pull Request

## License

This project is licensed under the MIT License - see the [LICENSE](LICENSE) file for details.

## Acknowledgments

- Built with [Bun](https://bun.sh)
- Uses [Solana Web3.js](https://github.com/solana-labs/solana-web3.js)
npm package: @nitive/github-bot-istanbul-coverage-100
Description: Github bot to ensure that your app have 100% coverage. It checks your coverage report and creates checks in pull requests, send coverage comments and annotate uncovered lines of code.
Latest version: 0.1.6

# Istanbul Coverage 100 [![Build Status](https://travis-ci.com/Nitive/github-bot-istanbul-coverage-100.svg?branch=master)](https://travis-ci.com/Nitive/github-bot-istanbul-coverage-100)

Github bot to ensure that your app have 100% coverage. It checks your coverage report and creates checks in pull requests, send coverage comments and annotate uncovered lines of code.

## Get started
1. Create github app, ask permissions for Pull Requests and Checks
1. Set env variables `GITHUB_APP_ID` and `GITHUB_APP_PRIVATE_KEY` in travis
1. Install `github-bot-istanbul-coverage-100` as dev dependency
1. Add `--coverage` flag to `jest` to collect coverage on CI
1. Add `json-summary` to coverage reporters
1. Add `npx github-bot-istanbul-coverage-100` in `after_success` script in .travis.yml
npm package: @nitive/nightwatch-image-comparison
Description: Screenshot assertions for Nightwatch
Author: Maxim Samoilov
Latest version: 0.1.2

# Nightwatch Image Comparison

Nightwatch assertions to compare screenshots in your tests.
Currently under development and contains a bunch of hardcoded options. Do not use yet, but please let me know if you want too.

## Credits

The module is now based on [webdriver-image-comparison module](https://github.com/wswebcreation/webdriver-image-comparison).
Thanks a lot [Wim Selles](https://github.com/wswebcreation) for creating and open sourcing it!

## Setting up

1. Install module `npm install --save-dev @nitive/nightwatch-image-comparison`
2. Configure module in `nightwatch.conf.js`

```js
const path = require('path')
const nightwatchImageComparison = require('@nitive/nightwatch-image-comparison')

module.exports = {
  globals: {
    screenshots: {
      testsRootDir: path.join(__dirname, 'tests'), // required
      screenshotsRootDir: path.join(__dirname, 'screenshots'), // required
      skipScreenshotAssertions: false, // default: false
    },
  },
  custom_assertions_path: [nightwatchImageComparison.assertionsPath],
}
```

## Usage examples

Making screenshot of all page

```js
browser.assert.screenshotPage('full authorization page')
```

Make a screenshot of element with selector `[data-test-id="auth-form"]`

```js
browser.assert.screenshotElement(
  '[data-test-id="auth-form"]',
  'Authorization form before filling: every field is empty'
)
```

Specifing allowed mismatch percentage. Try not to use it because it can lead to missing unexpected changes.

```js
browser.assert.screenshotElement(
  '[data-test-id="confirm-registration-form"]',
  'Confirmation form: fields are empty, submit button is disabled',
  {
    // Rendering in IE is slightly different every time
    allowedMisMatchPercentage: 0.5, // 0,5%
  }
)
```

Hide some selectors before taking screenshot

```js
browser.assert.screenshotElement(
  '[data-test-id="confirm-registration-form"]',
  'форма подтверждения регистрации: поля не заполнены, кнопка отправки задизейблена',
  {
    hideSelectors: [
      // Email is different every test run (created randomly)
      '[data-test-id="auth-form-email-field"]',
    ],
  }
)
```

## Best practices

- It's best to describe expected screenshot content. It will help to validate screenshots on code review.
- Use [Git LFS](https://git-lfs.github.com) to store a lot of images in repository