chore: migrate from pnpm to bun (#369)

## Summary

- Switch monorepo package manager from pnpm to Bun
- Remove deprecated `@mheob/eslint-config` and `@mheob/prettier-config` packages
- Add `baseJsConfig` to `@mheob/oxlint-config` for opt-in regexp plugin rules

## Changes

- **Package manager**: Replace pnpm workspaces + `pnpm-lock.yaml` with Bun workspaces + `bun.lock`; add `bunfig.toml`
- **CI/CD**: Switch GitHub Actions from `pnpm/action-setup` + `setup-node` to `oven-sh/setup-bun`
- **Husky hooks**: Replace `pnpm exec` with `bunx`; remove `use-correct-pm` check
- **Dependencies**: Replace pnpm `catalog:` references with explicit versions in all `package.json` files
- **Removed packages**: Delete `packages/eslint-config` and `packages/prettier-config` (superseded by oxlint/oxfmt)
- **Removed cursor rules**: Remove `.cursor/rules/` directory
- **oxlint-config**: Extract regexp plugin rules from `baseConfig` into a new `baseJsConfig` that consumers can opt into
- **Docs**: Update `CLAUDE.md`, `CONTRIBUTING.md`, `README.md` files, and Claude agent/skill configs

## Motivation

Bun is significantly faster than pnpm for installs and script execution, and it natively supports workspaces without a separate workspace YAML file. The `eslint-config` and `prettier-config` packages have been superseded by the Rust-based `oxlint-config` and `oxfmt-config` packages which are already in use.

## Breaking Changes

- `@mheob/eslint-config` and `@mheob/prettier-config` are no longer published from this repository
- `baseConfig` in `@mheob/oxlint-config` no longer includes regexp rules; use the new `baseJsConfig` instead


## Summary by CodeRabbit

* **New Features**
  * Added a JavaScript-focused lint config export (baseJsConfig) and a JS-specific config set.

* **Breaking Changes**
  * Tooling and CI migrated from pnpm/Node scripts to Bun; repo scripts and workflows now expect Bun/Node ≥24.
  * Legacy ESLint/Prettier package surfaces removed—migrate to OXLint/OXFmt configs.

* **Documentation**
  * Many READMEs and contribution docs updated with Bun commands, peer-dep instructions, and config usage examples.

Author: mheob

.changeset/readme-oxlint-config.md

@@ -0,0 +1,13 @@
+---
+'@mheob/oxlint-config': patch
+---
+
+docs: rewrite README to accurately reflect the source code
+
+- Document the previously missing `baseJsConfig` export and its JS plugins (`regexp`, `jsonc`, `yml`)
+- Fix `baseConfig` plugin table (remove plugins that belong to `baseJsConfig`)
+- Remove non-existent `toml` plugin section
+- Correct `tailwindcss/` rule prefixes to `better-tailwindcss/`
+- Add `react-hooks` to the `reactConfig` plugin table
+- Add peer dependency install snippets for optional configs
+- Replace all `ni` install commands with `bun add -D`

.claude/agents/git-versioning.md

@@ -29,7 +29,7 @@ best practices. You help developers create clean, meaningful version history tha
 
 ## Commit Message Convention
 
-This project uses **Commitizen** (`nr commit` is available), so follow the **Conventional Commits** specification strictly:
+This project uses **Commitizen** (`bun run commit` is available), so follow the **Conventional Commits** specification strictly:
 
 ```
 <type>(<scope>): <subject>
@@ -107,9 +107,9 @@ When creating branches, use the pattern: `<type>/<short-description>` Examples:
 
 Before creating commits, consider running relevant checks:
 
-- `nr lint` - Ensure no linting errors
-- `nr typecheck` - Ensure TypeScript compiles
-- `nr test` - Ensure tests pass
+- `bun run lint` - Ensure no linting errors
+- `bun run typecheck` - Ensure TypeScript compiles
+- `bun run test` - Ensure tests pass
 
 If any checks fail, inform the user and suggest fixes before committing.
 

.claude/skills/create-commit/SKILL.md

@@ -16,7 +16,7 @@ agent: git-versioning
 ## Your tasks
 
 - make a feature branch is active
-- create changeset if needed (at least an empty changeset); don't write the change message too short
+- create changeset for each commit (at least an empty one, if no changeset is needed); don't write the change message too short
 - create a single git commit or multiple commits if it makes more sense based on the above changes
 
 ## Structure
@@ -44,9 +44,8 @@ Describe the area of the codebase affected by the change, e.g. `feat(auth): add
 
 **Package scopes** (one per package):
 
-- `eslint` — `@mheob/eslint-config`
+- `oxfmt` — `@mheob/oxfmt-config`
 - `oxlint` — `@mheob/oxlint-config`
-- `prettier` — `@mheob/prettier-config`
 - `internal` — `@mheob/internal`
 - `tsconfig` — `@mheob/tsconfig`
 

.claude/skills/create-pr/SKILL.md

@@ -2,25 +2,20 @@
 name: create-pr
 description: Create a Pull Request
 user-invocable: true
-allowed-tools: Bash(az*), Bash(git*), Bash(nr*)
+allowed-tools: Bash(gh*), Bash(git*), Bash(bun run*)
 agent: git-versioning
 ---
 
-Create a _DRAFT_ Pull Request based on all commits in the current branch that differ from `develop`.
+Create a Pull Request based on all commits in the current branch that differ from `develop`.
+
+Check for an available changeset.
 
 - the title is written as conventional commit with a max length of 50 characters
 - the description is organized in "Summary", "Changes", "Motivation" and if useful any additional context
-- use our template: @.azuredevops/pull_request_template.md
 
 Make sure the description is clear and concise, and that it provides enough information for reviewers to understand the purpose
 and impact of the changes.
 
-If possible extract the Jira ticket number (NBP-0000) from the branch name and replace all instances of `NBP-XXX` in the
-description.
-
-Use Azure DevOps as remote. If you can use the Azure DevOps MCP us it, otherwise make sure the `az` CLI should be installed and
-configured. If not describe how to use the `az` CLI to create the PR on Azure DevOps.
-
 Do not use the `--no-verify` if not really need.
 
 Do not mention an co-author or generator.

.cspell.json

@@ -11,14 +11,12 @@
 		"**/package.json",
 		"**/pnpm-lock.yaml",
 		"**/pnpm-workspace.yaml",
-		"**/turbo.json",
-		"packages/eslint-config/src/typegen.d.ts",
+		"**/turbo.json"
 	],
 	"import": ["@cspell/dict-de-de/cspell-ext.json"],
 	"language": "en,de,lorem",
 	"version": "0.2",
 	"words": [
-		"antfu",
 		"astro",
 		"backreference",
 		"breakline",
@@ -53,6 +51,6 @@
 		"unocss",
 		"vitepress",
 		"vuejs",
-		"yoda",
-	],
+		"yoda"
+	]
 }