feat: add Clipboard to bronze sponsors

[zubhav]

Clipboard sponsors Zod ($100 p/m) so this change adds to the Bronze sponsors list

https://github.com/orgs/ClipboardHealth/sponsoring

Summary by CodeRabbit

• Chores

  • Migrated project tooling from Yarn/Jest/ESLint/Prettier to pnpm/Vitest/Biome, updating scripts, configs, and workspace settings.
  • Updated .gitignore to cover new build artifacts and directories.
  • Switched to modern monorepo-style setup with updated dependencies and scripts.
  • Changed Node.js version specification to 22.
  • Updated license year to 2025.

• Documentation

  • Removed or updated several documentation files, including migration guides, error handling, and non-English README.
  • Added and updated contributor and pull request guidelines.
  • Deleted the changelog and various blog and HTML documentation files.

• Tests

  • Removed extensive legacy test suites and benchmarking scripts.
  • Added new benchmarking scripts for array parsing.

• Configuration

  • Replaced and removed various configuration files for build, linting, formatting, and testing.
  • Introduced new configuration files for Biome, pnpm, and workspace management.
  • Updated VSCode and devcontainer settings for new toolchain.

• Refactor

  • Removed or replaced legacy scripts, helper utilities, and internal aggregation files to align with the new project structure.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

This update overhauls the project's configuration, tooling, and documentation. It removes a large number of test files, benchmarks, helpers, and legacy configs, while introducing new configs for Biome, pnpm, and Rollup. The package manager is switched to pnpm, and the project structure is modernized with updated scripts, workspace settings, and linting/formatting tools.

Changes

Files / Paths	Change Summary
.changeset/README.md, .changeset/config.json	Added README and config for Changesets, documenting the directory's purpose and specifying schema version, changelog, commit behavior, and branch settings.
.configs/rollup.config.js, .configs/tsconfig.base.json	Introduced new Rollup and TypeScript base config files for bundling and type-checking, specifying entry/output, plugins, tree-shaking, and strict compiler options.
.dependency-cruiser.js, .eslintrc.js, .prettierrc.yaml	Deleted configuration files for Dependency Cruiser, ESLint, and Prettier, removing related linting and dependency rules.
.devcontainer/devcontainer.json, .husky/pre-commit, .husky/pre-push	Updated devcontainer to use pnpm, simplified pre-commit to only run lint-staged with verbose output, and switched pre-push test command from yarn to pnpm.
.github/pull_request_template.md, .github/workflows/release-beta.yaml	Added PR template with branch guidance and a new GitHub Actions workflow for beta releases on the v4 branch.
.github/workflows/release-canary.yml, .github/workflows/release.yml	Commented out all steps in the canary release workflow; in the main release workflow, replaced yarn with pnpm, enabled dry-run for npm publish, and commented out changelog and release creation steps.
.github/workflows/test.yml	Updated test workflow to include v4 branch, switched from yarn to pnpm, removed Deno tests, and updated TypeScript versions in the matrix.
.gitignore	Expanded ignored files and directories to include new build artifacts, temp files, and package-related folders.
.npmrc, .nvmrc, biome.jsonc	Added npm workspace config, Node version file, and Biome config for formatting, linting, and ignoring files.
.vscode/launch.json, .vscode/settings.json	Updated VSCode launch configs to separate Node and tsx debugging, switched formatter to Biome, refined import organization, and updated file excludes.
CHANGELOG.md, ERROR_HANDLING.md, FUNDING.json, MIGRATION.md, README_ZH.md, _redirects, blog/*, index.html	Deleted changelog, error handling guide, funding info, migration guide, Chinese README, redirects, blog files, and main documentation HTML.
CONTRIBUTING.md	Updated contributing guide to use pnpm and Vitest, reverted branch naming to master, and clarified test instructions.
configs/*, jest.config.json	Deleted all legacy configs for Babel, Jest, SWC, Rollup, and multiple TypeScript builds.
package.json	Major overhaul: switched to private, module type, pnpm, removed old fields, replaced scripts, updated devDependencies, and restructured lint-staged and workspace settings.
deno-build.mjs, deno/lib/*, index.d.ts	Deleted Deno build script, all Deno library files, helpers, locales, benchmarks, and the main type declaration file, removing all related exports and test code.
packages/bench/_temp.ts, packages/bench/array.ts	Added new benchmarking scripts for array parsing using zod3 and zod4, with test data generation and performance measurement.

Sequence Diagram(s)

sequenceDiagram
    participant Dev as Developer
    participant VSCode as VSCode
    participant Biome as Biome
    participant pnpm as pnpm
    participant GitHub as GitHub Actions

    Dev->>VSCode: Open project
    VSCode->>Biome: Format and lint code on save
    Dev->>pnpm: Run scripts (build, test, lint)
    pnpm->>Biome: Lint/format as per new config
    pnpm->>pnpm: Install dependencies
    Dev->>GitHub: Push changes / PR
    GitHub->>GitHub: Run updated workflows (test, release)

Loading

Possibly related PRs

• colinhacks/zod#4218: Adds the same .changeset and .configs files, indicating a direct overlap in configuration and setup changes.
• colinhacks/zod#4226: Also introduces or modifies .changeset/README.md, .changeset/config.json, .configs/rollup.config.js, and .configs/tsconfig.base.json, showing strong configuration-level relation.
• colinhacks/zod#4253: Adds similar Changesets and configuration files, reflecting a shared focus on project tooling and setup.

Poem

Out with the old, in with the new,
pnpm and Biome now guide us through.
Configs are trimmed, the scripts are tight,
Deno and legacy fade out of sight.
Fresh benchmarks run, the workspace is clean—
Zod’s future is bright, and the tooling’s serene!
✨🧹🚀

Note

⚡️ AI Code Reviews for VS Code, Cursor, Windsurf

CodeRabbit now has a plugin for VS Code, Cursor and Windsurf. This brings AI code reviews directly in the code editor. Each commit is reviewed immediately, finding bugs before the PR is raised. Seamless context handoff to your AI code agent ensures that you can easily incorporate review feedback.
Learn more here.

---

Note

⚡️ Faster reviews with caching

CodeRabbit now supports caching for code and dependencies, helping speed up reviews. This means quicker feedback, reduced wait times, and a smoother review experience overall. Cached data is encrypted and stored securely. This feature will be automatically enabled for all accounts on May 30th. To opt out, configure Review - Disable Cache at either the organization or repository level. If you prefer to disable all data retention across your organization, simply turn off the Data Retention setting under your Organization Settings.
Enjoy the performance boost—your workflow just got faster.

✨ Finishing Touches

• 📝 Generate Docstrings

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.