open-index/open-npm huggingface dataset:
npm package: @hybrbase-front/tailwind-presets
Description: - A Tailwind CSS frontend preset includes design system from themes package
Latest version: 1.0.1

# tailwind-preset

- A Tailwind CSS frontend preset includes design system from themes package

## Installation

aaaa

```sh
yarn add @hybrbase-front/tailwind-presets
# or
npm i @hybrbase-front/tailwind-presets
```
npm package: @hybrbase-staxomni/tailwind-presets
Description: - A Tailwind CSS frontend preset includes design system from themes package
Latest version: 1.0.3

# tailwind-preset

- A Tailwind CSS frontend preset includes design system from themes package

## Installation

aaaa

```sh
yarn add @hybrbase-staxomni/tailwind-presets
# or
npm i @hybrbase-staxomni/tailwind-presets
```
npm package: @hybrbase/htmlhint-config
Description: A shareable htmlhint configuration for projects.
Author: Toby Bui
Latest version: 0.0.0

# Shareable Htmlhint Config

## 📄 About

Package that contains shareable configurations for [HTMLHint](https://github.com/htmlhint/HTMLHint) — a popular linting tool that helps to identify and fix problems in your HTML code.

### → Purpose

This package aims to provide a shared set of rules for [HTMLHint](https://github.com/htmlhint/HTMLHint) to ensure consistent coding practices across a team or organization.

- Provide a shared configuration that helps avoid inconsistencies and ensures that everyone follows the latest best practices and guidelines.
- Make it easier for teams to use [HTMLHint](https://github.com/htmlhint/HTMLHint) effectively and improve the quality of their HTML code.

<br>

## 💿 Installation

To use this configuration, you'll need to install the `htmlhint` and `@hybrbase/htmlhint-config` packages as devDependencies in your project. These packages should be installed in the `package.json` file of the specific app or package that needs them:

```bash
pnpm --filter=my-first-app add -D htmlhint @hybrbase/htmlhint-config
```

This package should be added to the root of your monorepo, where you have a file `.htmlhintrc` and a `package.json` file. Within your monorepo, you should have a structure with directories for your apps and packages, such as:

```bash
.
├── package.json (root)
├── apps
│   └── my-first-app
│       ├── package.json
│       └── ... (other app files)
└── packages
    └── my-first-package
        ├── package.json
        └── ... (other package files)
```

### → Configure

To configure the `htmlhint`, add script to `package.json`

```bash
pnpm pkg set scripts.lint:html="htmlhint --config ./node_modules/@hybrbase/htmlhint-config/index.json **/*.html"
```

<br>

## 💻 Usage

You can run the `htmlhint` command manually using the following `pnpm` command:

```bash
pnpm --filter=my-first-app lint:html
```
npm package: @hybrbase/jest-config
Description: A shareable jest configuration for projects.
Author: Toby Bui
Latest version: 0.0.0

# Shareable Secretlint Config

## 📄 About

Shareable configuration for [Secretlint](https://github.com/secretlint/secretlint) — a tool for linting and fixing secrets in your codebase.

The configuration provides a set of rules and settings that can be easily shared and reused across different projects, reducing the amount of boilerplate code needed to set up [Secretlint](https://github.com/secretlint/secretlint) in each project.

### → Purpose

Simplify the process of setting up Secretlint in a project by providing a pre-configured set of rules and settings. This package can be useful for developers who want to:

- Use Secretlint in their project but don't want to spend time configuring it from scratch
- Share Secretlint configuration across multiple projects
- Avoid maintaining and updating Secretlint configuration in every project manually

The configuration includes a set of preconfigured rules, such as `@secretlint/secretlint-rule-preset-recommend`, that check for common mistakes and prevent secrets from being accidentally committed to the repository.

<br>

## 💿 Installation

To use Secretlint with `@hybrbase/secretlint-config` in a mono-repository, you can install them at the root level and configure it to lint only the packages that require it. Follow these steps:

1. Install `secretlint` and `@hybrbase/secretlint-config` as development dependencies at the root of your mono-repository using the package manager of your choice (`npm`, `yarn`, `pnpm`, etc.). For example, using `pnpm`:

   ```bash
   pnpm add -Dw secretlint @hybrbase/secretlint-config
   ```

2. Create a `.secretlintrc.json` configuration file in the root of your mono-repository with the following content:

   ```json
   {
     "rules": {},
     "rulesConfig": {},
     "plugins": [],
     "processor": "",
     "noDefaultConfig": true,
     "configs": {
       "@hybrbase/secretlint-config": true
     },
     "ignore": [],
     "include": ["packages/*/**", "apps/*/**"]
   }
   ```

   In this example, Secretlint is configured to use the `@hybrbase/secretlint-config` package as its configuration, and to lint only the directories in the `packages` and `apps` folders of the mono-repository.

   You can adjust the `include` and `exclude` patterns to match your specific mono-repository structure and exclude files or directories that don't need to be linted.

3. Add a linting script to the `scripts` section of the `package.json` file at the root of your mono-repository:

   ```bash
   pnpm pkg set scripts.lint:secrets="secretlint"
   ```

   This will add the `lint:secrets` script to the `scripts` section of your `package.json`.

That's it! You can now run the `lint:secrets` script to lint the relevant packages in your mono-repository.
npm package: @hybrbase/markdownlint-config
Description: A shareable markdownlint configuration for projects.
Author: Toby Bui
Latest version: 0.0.0

# Shareable Markdownlint Config

## 📄 About

Shareable configuration package for [markdownlint](https://github.com/DavidAnson/markdownlint) — a popular linter for Markdown files.

This package provides a consistent and standardized configuration for Markdown linters across projects. By using this package, you can ensure that your Markdown files adhere to the same set of rules and guidelines, improving their readability and maintainability.

### → Purpose

- Make it easy for developers to create Markdown files that meet a minimum standard of quality
- Provide a consistent and standardized configuration for Markdown linters across projects
- Save time and effort by avoiding the need to manually configure markdownlint for each project
- Improve the readability and maintainability of Markdown files

<br>

## 💿 Installation

To use this configuration, you'll need to install `@hybrbase/markdownlint-config` as a development dependency in your mono-repository.

```bash
# Install as dev-dependency in the root of the mono-repository
$ pnpm add -wD \
 markdownlint \
 markdownlint-cli \
 @hybrbase/markdownlint-config
```

This package should be installed in the root of your mono-repository, where you will create a file `.markdownlint.json`. Within your monorepo, you should have a structure with directories for your apps and packages, such as:

```bash
.
├── .markdownlint.json (root)
├── package.json (root)
├── apps
│   └── my-first-app
│       ├── package.json
│       └── ... (other app files)
└── packages
    └── my-first-package
        ├── package.json
        └── ... (other package files)
```

### → Configure

1. Create `.markdownlint.json` file in root of mono-repository and add lines:

   ```json
   {
     "extends": "./node_modules/@hybrbase/markdownlint-config/base.json"
   }
   ```

2. Add scripts to your `package.json`:

   ```bash
   pnpm pkg set scripts.lint:md="markdownlint --fix **/*.md --ignore '**/node_modules/**' --ignore '**/CHANGELOG.md'"
   ```
npm package: @hybrbase/secretlint-config
Description: A shareable secretlint configuration for projects.
Author: Toby Bui
Latest version: 0.0.0

# Shareable Secretlint Config

## 📄 About

Shareable configuration for [Secretlint](https://github.com/secretlint/secretlint) — a tool for linting and fixing secrets in your codebase.

The configuration provides a set of rules and settings that can be easily shared and reused across different projects, reducing the amount of boilerplate code needed to set up [Secretlint](https://github.com/secretlint/secretlint) in each project.

### → Purpose

Simplify the process of setting up Secretlint in a project by providing a pre-configured set of rules and settings. This package can be useful for developers who want to:

- Use Secretlint in their project but don't want to spend time configuring it from scratch
- Share Secretlint configuration across multiple projects
- Avoid maintaining and updating Secretlint configuration in every project manually

The configuration includes a set of preconfigured rules, such as `@secretlint/secretlint-rule-preset-recommend`, that check for common mistakes and prevent secrets from being accidentally committed to the repository.

<br>

## 💿 Installation

To use Secretlint with `@hybrbase/secretlint-config` in a mono-repository, you can install them at the root level and configure it to lint only the packages that require it. Follow these steps:

1. Install `secretlint` and `@hybrbase/secretlint-config` as development dependencies at the root of your mono-repository using the package manager of your choice (`npm`, `yarn`, `pnpm`, etc.). For example, using `pnpm`:

   ```bash
   pnpm add -Dw secretlint @hybrbase/secretlint-config
   ```

2. Create a `.secretlintrc.json` configuration file in the root of your mono-repository with the following content:

   ```json
   {
     "rules": {},
     "rulesConfig": {},
     "plugins": [],
     "processor": "",
     "noDefaultConfig": true,
     "configs": {
       "@hybrbase/secretlint-config": true
     },
     "ignore": [],
     "include": [
       "packages/*/**",
       "apps/*/**"
     ]
   }
   ```

   In this example, Secretlint is configured to use the `@hybrbase/secretlint-config` package as its configuration, and to lint only the directories in the `packages` and `apps` folders of the mono-repository.

   You can adjust the `include` and `exclude` patterns to match your specific mono-repository structure and exclude files or directories that don't need to be linted.

3. Add a linting script to the `scripts` section of the `package.json` file at the root of your mono-repository:

   ```bash
   pnpm pkg set scripts.lint:secrets="secretlint"
   ```

   This will add the `lint:secrets` script to the `scripts` section of your `package.json`.

That's it! You can now run the `lint:secrets` script to lint the relevant packages in your mono-repository.