Contributions are welcome as long as they stay focused on formatting behavior, parser correctness, or test coverage.
-
Fork the repository and create a feature branch.
-
Install dependencies:
bun install
-
Keep the scope narrow. One fix or feature per pull request is easier to review and safer to merge.
- Follow the repository's existing structure and naming patterns.
- Add or update tests for functional changes.
- Keep documentation aligned with code changes.
- Prefer small, readable diffs over broad refactors.
Dependabot checks the Bun ecosystem weekly and targets dev. Keep package.json and bun.lock updated together. Use bun outdated to check available versions and validate major upgrades before merging them. No Dev Container update job is configured because this repository does not contain a Dev Container configuration.
Before opening or updating a PR, run the repository checks:
bun run lint
bun run format:check
bun testFor quick iteration during development, this workflow is also useful:
bun run example
bun test- Create a branch for your change.
- Implement the fix or feature.
- Add the relevant tests.
- Run the validation commands above.
- Open a PR with a clear summary and the specific behavior it changes.
If the change affects user behavior, parser rules, or release workflow, update the relevant docs in docs/development and, when needed, the root README.md.
Open an issue before starting a large change if the expected behavior is not yet clear. That helps keep the contribution aligned with the project's direction.