docsearch/CONTRIBUTING.md

Contributing to DocSearch

Welcome to the contributing guide for DocSearch!

If this guide does not contain what you are looking for and thus prevents you from contributing, don't hesitate to leave a message on the Discord or to open an issue.

Reporting an issue

Opening an issue is very effective way to contribute because many users might also be impacted. We'll make sure to fix it quickly if it's technically feasible and doesn't have important side effects for other users.

Before reporting an issue, first check that there is not an already open issue for the same topic using the issues page. Don't hesitate to thumb up an issue that corresponds to the problem you have.

Another element that will help us go faster at solving the issue is to provide a reproducible test case. We recommend to use this CodeSandbox template.

Code contribution

For any code contribution, you need to:

• Fork and clone the project
• Create a new branch for what you want to solve (fix/issue-number, feat/name-of-the-feature)
• Make your changes
• Open a pull request

Then:

• A team member will review the pull request
• Automatic checks will be run

When every check is green and a team member approves, your contribution is merged! 🚀

Commit conventions

This project follows the conventional changelog approach. This means that all commit messages should be formatted using the following scheme:

type(scope): description

In most cases, we use the following types:

• fix: for any resolution of an issue (identified or not)
• feat: for any new feature
• refactor: for any code change that neither adds a feature nor fixes an issue
• docs: for any documentation change or addition
• chore: for anything that is not related to the library itself (doc, tooling)

Even though the scope is optional, we try to fill it in as it helps us better understand the impact of a change.

Finally, if your work is based on an issue on GitHub, please add in the body of the commit message "fix #1234" if it solves the issue #1234 (read "Closing issues using keywords").

Some examples of valid commit messages (used as first lines):

• fix(searchbox): add type input property
• chore(deps): update dependency rollup-plugin-babel to v3.0.7
• fix(modal): increase default height
• docs(contributing): reword release section

Requirements

To run this project, you will need:

• Node.js ≥ 18 – nvm is recommended
• Bun – our package manager and build tool

Getting started

# Install dependencies
bun install

# Build all packages
bun run build

# Run tests
bun run test

# Start development mode (watch + playground)
bun run dev

Changesets

This project uses Changesets for versioning and publishing.

If your PR includes changes that should be released, add a changeset:

bun run changeset

Select the packages affected by your change, choose the version bump type (major/minor/patch), and write a summary that will appear in the changelog.

Release

When changesets are merged to main, a "Version Packages" PR will be automatically created (or updated). Merging that PR triggers the release workflow:

1. Package versions are bumped
2. CHANGELOGs are updated
3. Packages are published to npm
4. Git tags are created

All @docsearch/* packages share the same version number (fixed versioning).