open-index/open-npm huggingface dataset:
npm package: @jszymanowski/biomejs-config
Description: My personal biome.js config
Author: John Szymanowski
Latest version: 1.2.0
Deprecated: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.

This is my personal [biome](https://biomejs.dev) configuration.  It's currently based on the [2.0.0 beta](https://biomejs.dev/blog/biome-v2-0-beta/), as I've experienced a number of issues with recent stable 1.9.x release in multi-root workplaces.  2.0.0-beta1 seems to resolve these.


### Key features
- Uses `.gitignore` to avoid formatting unuseful files and directories
- Up to 100 chars per line
- Spacing: spaces instead of tabs, 2 instead of 4
- JavaScript: double quotes, trailing commas, semicolons

### Usage
Firstly, install [biome](https://biomejs.dev) and this [configuration](https://www.npmjs.com/package/@jszymanowski/biomejs-config):

```bash
pnpm i -D --save-exact @jszymanowski/biomejs-config @biomejs/biome@beta
```

Then, add the following to your `biome.json`:

```json
{
  "$schema": "https://biomejs.dev/schemas/2.0.0-beta.1/schema.json",
  "extends": ["@jszymanowski/biomejs-config"]
}
```

And finally, add the following scripts to your `package.json` to easily format and lint your code:

```json
{
  "scripts": {
    "format": "biome format --write .",
    "lint": "biome check .",
    "lint:ci": "biome ci .",
    "lint:fix": "biome check --write --unsafe ."
  }
}
```
npm package: @jszymanowski/breeze
Description: Primitive React components, built with Tailwind CSS
Author: John Szymanowski
Latest version: 0.4.0
Deprecated: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.

# Breeze Primitives

_Primitive React components, built with Tailwind CSS_

---

### Publishing

Automatic:

```bash
pnpm version patch -m "Release %s"
git push && git push --tags
```

Manual:

```bash
git tag primitives@0.1.6
git push origin primitives@0.1.6
```
npm package: @jszymanowski/breeze-charts
Description: React chart components, built with Tailwind CSS and VisX
Author: John Szymanowski
Latest version: 0.3.0
Deprecated: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.

# Breeze Charts

_React chart components, built with Tailwind CSS and VisX_

[![codecov](https://codecov.io/gh/jszymanowski/breeze/branch/main/graph/badge.svg)](https://codecov.io/gh/jszymanowski/breeze)

---

### Releases & Publishing

Releases are automated using [Release Please](https://github.com/googleapis/release-please):

1. When a PR is merged to main, Release Please will analyze recent commits to determine if and how a release should be structured.
1. A PR with necessary changes to make a release will be opened. This will include:
   - version bump
   - [changelog](./CHANGELOG.md) updates
1. Once merged, the release will be completed but not published. Release Please will:
   - create a Git tag (like v1.2.3) corresponding to the released version
   - create a GitHub Release with the changelog as release notes
1. The [`publish` Github Action](../../.github/workflows/publish.yml) will detect the new tag and publish the release.
1. The new version will be available from the [NPM registry](https://www.npmjs.com/package/@jszymanowski/breeze-charts)
npm package: @jszymanowski/breeze-forms
Description: React form components, built with Tailwind CSS and ShadCN
Author: John Szymanowski
Latest version: 0.7.0
Deprecated: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.

# Breeze Forms

_React form components, built with Tailwind CSS and ShadCN_

[![codecov](https://codecov.io/gh/jszymanowski/breeze/branch/main/graph/badge.svg)](https://codecov.io/gh/jszymanowski/breeze)

**Resources**

- [Github repo](https://github.com/jszymanowski/breeze)
- Distribution
  - [npm registry](https://www.npmjs.com/package/@jszymanowski/breeze-primitives)
- Building blocks
  - [TailwindCSS](https://tailwindcss.com/docs)
  - [shadcn-ui](https://ui.shadcn.com/docs/)
    - [color themes](https://ui.shadcn.com/colors)
  - [Vite](https://vite.dev/guide/)
  - [Vitest](https://vitest.dev/guide/)
- Documentation via Storybook
  - [Github Pages](https://jszymanowski.github.io/breeze/) - docs only
  - [Chromatic](https://67ccefd8fafa91b1c6c38501-dubbfpsqzi.chromatic.com/) - full suite of stories
- Development
  - [Chromatic builds](https://www.chromatic.com/builds?appId=67ccefd8fafa91b1c6c38501)
  - [CodeCov](https://app.codecov.io/gh/jszymanowski/breeze)
  - [Renovate](https://developer.mend.io/github/jszymanowski/breeze)
- Other documentation, documents
  - [Changelog](./CHANGELOG.md)
  - [Roadmap](./docs/ROADMAP.md)

---

## Usage

### Installation

When using Vite, Breeze must be included in your primary `.css` file in order to ensure the necessary CSS classes are included in the build. For more details, read the Tailwind CSS documentation on [explicitly registering sources](https://tailwindcss.com/docs/detecting-classes-in-source-files#explicitly-registering-sources).

Example `index.css`:

```css
@import "tailwindcss";
@source "../node_modules/@jszymanowski/breeze-primitives/dist";

@layer base {
  /* your usual CSS definitions */
}
```

---

### Releases & Publishing

Releases are automated using [Release Please](https://github.com/googleapis/release-please):

1. When a PR is merged to main, Release Please will analyze recent commits to determine if and how a release should be structured.
1. A PR with necessary changes to make a release will be opened. This will include:
   - version bump
   - [changelog](./CHANGELOG.md) updates
1. Once merged, the release will be completed but not published. Release Please will:
   - create a Git tag (like v1.2.3) corresponding to the released version
   - create a GitHub Release with the changelog as release notes
1. The [`publish` Github Action](../../.github/workflows/publish.yml) will detect the new tag and publish the release.
1. The new version will be available from the [NPM registry](https://www.npmjs.com/package/@jszymanowski/breeze-primitives)
npm package: @jszymanowski/breeze-primitives
Description: Primitive React components, built with Tailwind CSS
Author: John Szymanowski
Latest version: 0.9.0
Deprecated: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.

# Breeze Primitives

_Primitive React components, built with Tailwind CSS_

[![codecov](https://codecov.io/gh/jszymanowski/breeze/branch/main/graph/badge.svg)](https://codecov.io/gh/jszymanowski/breeze)

**Resources**

- [Github repo](https://github.com/jszymanowski/breeze)
- Distribution
  - [npm registry](https://www.npmjs.com/package/@jszymanowski/breeze-react)
- Building blocks
  - [TailwindCSS](https://tailwindcss.com/docs)
  - [shadcn-ui](https://ui.shadcn.com/docs/)
    - [color themes](https://ui.shadcn.com/colors)
  - [Vite](https://vite.dev/guide/)
  - [Vitest](https://vitest.dev/guide/)
- Documentation via Storybook
  - [Github Pages](https://jszymanowski.github.io/breeze/) - docs only
  - [Chromatic](https://67ccefd8fafa91b1c6c38501-dubbfpsqzi.chromatic.com/) - full suite of stories
- Development
  - [Chromatic builds](https://www.chromatic.com/builds?appId=67ccefd8fafa91b1c6c38501)
  - [CodeCov](https://app.codecov.io/gh/jszymanowski/breeze)
  - [Renovate](https://developer.mend.io/github/jszymanowski/breeze)
- Other documentation, documents
  - [Changelog](./CHANGELOG.md)
  - [Roadmap](./docs/ROADMAP.md)

---

## Usage

### Installation

When using Vite, Breeze must be included in your primary `.css` file in order to ensure the necessary CSS classes are included in the build. For more details, read the Tailwind CSS documentation on [explicitly registering sources](https://tailwindcss.com/docs/detecting-classes-in-source-files#explicitly-registering-sources).

Example `index.css`:

```css
@import "tailwindcss";
@source "../node_modules/@jszymanowski/breeze-react/dist";

@layer base {
  /* your usual CSS definitions */
}
```

---

### Releases & Publishing

Releases are automated using [Release Please](https://github.com/googleapis/release-please):

1. When a PR is merged to main, Release Please will analyze recent commits to determine if and how a release should be structured.
1. A PR with necessary changes to make a release will be opened. This will include:
   - version bump
   - [changelog](./CHANGELOG.md) updates
1. Once merged, the release will be completed but not published. Release Please will:
   - create a Git tag (like v1.2.3) corresponding to the released version
   - create a GitHub Release with the changelog as release notes
1. The [`publish` Github Action](../../.github/workflows/publish.yml) will detect the new tag and publish the release.
1. The new version will be available from the [NPM registry](https://www.npmjs.com/package/@jszymanowski/breeze-react)
npm package: @jszymanowski/breeze-react
Description: Primitive React components, built with Tailwind CSS
Author: John Szymanowski
Latest version: 0.8.0
Deprecated: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.

# Breeze React

_Primitive React components, built with Tailwind CSS_

[![codecov](https://codecov.io/gh/jszymanowski/breeze/branch/main/graph/badge.svg)](https://codecov.io/gh/jszymanowski/breeze)

**Resources**

- [Github repo](https://github.com/jszymanowski/breeze)
- Distribution
  - [npm registry](https://www.npmjs.com/package/@jszymanowski/breeze-react)
- Building blocks
  - [TailwindCSS](https://tailwindcss.com/docs)
  - [shadcn-ui](https://ui.shadcn.com/docs/)
    - [color themes](https://ui.shadcn.com/colors)
  - [Vite](https://vite.dev/guide/)
  - [Vitest](https://vitest.dev/guide/)
- Documentation via Storybook
  - [Github Pages](https://jszymanowski.github.io/breeze/) - docs only
  - [Chromatic](https://67ccefd8fafa91b1c6c38501-dubbfpsqzi.chromatic.com/) - full suite of stories
- Development
  - [Chromatic builds](https://www.chromatic.com/builds?appId=67ccefd8fafa91b1c6c38501)
  - [CodeCov](https://app.codecov.io/gh/jszymanowski/breeze)
  - [Renovate](https://developer.mend.io/github/jszymanowski/breeze)
- Other documentation, documents
  - [Changelog](./CHANGELOG.md)
  - [Roadmap](./docs/ROADMAP.md)

---

## Usage

### Installation

When using Vite, Breeze must be included in your primary `.css` file in order to ensure the necessary CSS classes are included in the build. For more details, read the Tailwind CSS documentation on [explicitly registering sources](https://tailwindcss.com/docs/detecting-classes-in-source-files#explicitly-registering-sources).

Example `index.css`:

```css
@import "tailwindcss";
@source "../node_modules/@jszymanowski/breeze-react/dist";

@layer base {
  /* your usual CSS definitions */
}
```

---

### Releases & Publishing

Releases are automated using [Release Please](https://github.com/googleapis/release-please):

1. When a PR is merged to main, Release Please will analyze recent commits to determine if and how a release should be structured.
1. A PR with necessary changes to make a release will be opened. This will include:
   - version bump
   - [changelog](./CHANGELOG.md) updates
1. Once merged, the release will be completed but not published. Release Please will:
   - create a Git tag (like v1.2.3) corresponding to the released version
   - create a GitHub Release with the changelog as release notes
1. The [`publish` Github Action](../../.github/workflows/publish.yml) will detect the new tag and publish the release.
1. The new version will be available from the [NPM registry](https://www.npmjs.com/package/@jszymanowski/breeze-react)
npm package: @jszymanowski/proper-date.js
Description: Simple, lightweight date object library for JavaScript/TypeScript, without the time nonsense.
Author: John Szymanowski
Latest version: 0.6.1
Deprecated: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.

# ProperDate.js

A simple, lightweight date object library for JavaScript/TypeScript, without the time and timezone nonsense.

[![codecov](https://codecov.io/gh/jszymanowski/proper-date.js/branch/main/graph/badge.svg)](https://codecov.io/gh/jszymanowski/proper-date.js)

## Usage

```js
import ProperDate from "@jszymanowski/proper-date.js";

const date = ProperDate("2024-12-25");
date.formatted; // '2024-12-25'

// and so on
```

## Package management

### Local testing

Testing this package as a dependency is easy with [Yalc](https://github.com/wclr/yalc):

```bash
# Install (depending on your preferred package manager)
npm i yalc -g
yarn global add yalc
pnpm add -g yalc

# Build this library, as usual:
pnpm build

# "Publish" this library locally (run in this directory)
yalc publish

# Link the locally "published" version of ProperDate.js (run in the consuming app/library)
## This will copy the local version of this library into the `.yalc` folder and modify your
## package.json to look for this library there.  You will want to add `.yalc` to your `.gitignore`,
## and be sure to change back to the real published version before shipping.
yalc add @jszymanowski/proper-date.js

# As needed: update the locally "published" package
yalc update @jszymanowski/proper-date.js
yalc update # all packages in yalc.lock

# When done
## In consuming app/library:
yalc remove @jszymanowski/proper-date.js
yalc remove --all # all packages in yalc.lock

## In this package:
yalc installations clean @jszymanowski/proper-date.js # unpublish / reverts yalc publish
```

### Publishing

Manual:

```bash
git tag v0.1.0
git push origin v0.1.0
```