open-index/open-npm huggingface dataset:
npm package: @haloforge/plugin-pack
Description: HaloForge plugin packager CLI — validate, build, and bundle plugins into .hfpkg archives
Latest version: 0.1.0

# @haloforge/plugin-pack

`@haloforge/plugin-pack` is the public HaloForge plugin packager CLI.

Use it to validate a plugin directory, inspect an existing `.hfpkg`, and produce a distributable package that HaloForge can install.

## Run With npx

```bash
npx @haloforge/plugin-pack check .
npx @haloforge/plugin-pack pack . --release
```

## Commands

```bash
hf-pack check <plugin-dir>
hf-pack info <plugin-dir-or-.hfpkg>
hf-pack pack <plugin-dir> [--out dist] [--release] [--no-backend] [--no-frontend] [--target <triple>]
```

## Supported Layout

```text
my-plugin/
  manifest.json
  backend/
    Cargo.toml
    src/
  frontend/
    package.json
    src/
  assets/
  LICENSE
```

The Rust backend can also live at the plugin root as `Cargo.toml` and `src/`.

The CLI also accepts these common variants:

- Backend in `backend/`, `native/`, `rust/`, or the plugin root.
- Frontend in `frontend/`, `ui/`, `web/`, `app/`, or the plugin root.
- Frontend builds emitted to `dist/`, `build/`, or `.output/`.

## What the CLI Does

1. Validates `manifest.json`.
2. Builds the Rust backend with `cargo build` unless `--no-backend` is used.
3. Builds the frontend app with the detected package manager unless `--no-frontend` is used.
4. Copies declared frontend outputs, packaged native binaries, optional `assets/`, and `LICENSE` into a staging directory.
5. Writes `<plugin-id>-<version>.hfpkg` to the output directory.

## Frontend Build Notes

- The CLI detects `npm`, `pnpm`, `yarn`, and `bun` from lockfiles.
- If `package.json` declares a `packageManager` field, the CLI prefers that over lockfile heuristics.
- Frontend output paths are taken from `manifest.json` via `entry.frontend` and `entry.frontend_styles`.
- If those files are actually emitted under `dist/`, `build/`, or `.output/`, the CLI remaps them back to the packaged paths declared in the manifest.
npm package: @halohubio/graphql_tailwind_base
Description: [![NPM](https://img.shields.io/npm/v/@halohubio/playground.svg)](https://www.npmjs.com/package/@dlarroder/playground) [![Downloads](https://img.shields.io/npm/dt/@halohubio/playground.svg)](https://www.npmjs.com/package/@dlarroder/playground)
Author: Ha Nguyen
Latest version: 0.1.11

# graphql_tailwind_base 

[![NPM](https://img.shields.io/npm/v/@halohubio/playground.svg)](https://www.npmjs.com/package/@dlarroder/playground)
[![Downloads](https://img.shields.io/npm/dt/@halohubio/playground.svg)](https://www.npmjs.com/package/@dlarroder/playground)

**graphql_tailwind_base** is a React component component library, as the name suggest, this will serve as my playground where I can 
show off some of the cool component ideas I have and will be available for the public to use via npm.

## Installing graphql_tailwind_base

To use graphql_tailwind_base components, all you need to do is install the `@halohubio/graphql_tailwind_base` package

```sh
$ yarn add @halohubio/graphql_tailwind_base

# or

$ npm i @halohubio/graphql_tailwind_base
```

## Usage

To start using the components, please follow these steps:

1. Import stylesheets manually

```jsx
import '@halohubio/graphql_tailwind_base/dist/styles.css'
```

2. Now you can start using components like so

```jsx
import { useState } from 'react'
import { Switch } from '@halohubio/graphql_tailwind_base'

function Example() {
  const [checked, setChecked] = useState(false)

  return <Switch checked={checked} onChange={setChecked} />
}
```