We can use help in a bunch of areas and any help is greatly appreciated!
- 🚀 Contributing
If you have any questions, proposals, or feedbacks, open a GitHub discussion. Make sure your comment adds value: don't post a comment just to get attention.
Our Discord server is open for help and more ad-hoc discussion. All activity on the Discord is still moderated and will be strictly enforced under the project's Code of Conduct.
Remember that we are doing this project on our own time. We are humans: we like support, and we expect kindness :)
Our GitHub issues serve as a place for submitting bugs. Make sure that the bugs is not reported yet and is not fixed in the main branch. You can test on the main branch, thanks to the playground.
Alternatively, you can use our official CodeSandbox template.
Building this project requires a stable Rust toolchain, which can be installed using rustup.
Clone the repository and navigate to the tools directory:
git clone https://github.com/biomejs/biome
cd biomeCompile all packages and dependencies:
cargo buildBiome can be used via the biome bin:
cargo run --bin biome -- --helpWe use Just to run scripts and tasks, to make our life easier.
You can install just using cargo:
cargo install justBut we highly recommend to install it using an OS package manager,
so you won't need to prefix every command with cargo.
Once installed, run the following command install the required tools:
just install-toolsAnd you're good to go hack with Biome and Rust! 🚀
To know the technical details of how our analyzer works, how to create a rule and how to write tests, please check our internal page
To know the technical details of how our parser works and how to write test, please check our internal page
To know the technical details of how our formatter works and how to write test, please check our internal page
To run the tests, just run
just testIf you want to test the tests for a single crate:
just test-crate biome_cliTo run only the doctests, you would need to pass an argument to the command:
just test-docIn some crates, we use snapshot testing.
The majority of snapshot testing is done using insta.
insta is already installed by the command just install-tools.
When a snapshot test fails, you can run:
cargo insta acceptto accept all the changes and update all the snapshots;cargo insta rejectto reject all the changes;cargo insta reviewto review snapshots singularly;
When you finished your work, and you are ready to commit and open a PR, run the following command:
just readyThis command will run the same commands of the CI: format, lint, tests and code generation. Eventually everything should be "green" 🟢 and commit all the code that was generated.
If you work on some parser and create new nodes or modify existing ones, you must run a command to update some auto-generated files.
This command will update the syntax of the parsers.
The source is generated from the ungram files.
This command will create new tests for JS or JSON pars A0A9 er. These tests are generated from inline comments found inside the source code.
On the other hand, we are moving away from this approach and have a straightforward process in other parser implementation like CSS.
This command will detect linter rules declared in the analyzers, assists and syntax directories in the analyzer crates, e.g. biome_js_analyze, biome_json_analyze, etc., and regenerate the registry.rs file and its dependents to include all the rules.
Workspace dependencies are used, and many dependencies are defined in Cargo.toml in the root.
Internal crates are loaded with workspace = true for each crate. About dev-dependencies, we use path dependencies to avoid requiring the published version of these crates.
The npm module npm/biome contains Biome's Node JS API that supports different backends:
wasm-nodejs(WebAssembly)backend-jsonrpc(Connection to the daemon)
For testing and developing, you need to build these packages, following the steps:
- install wasm-pack globally;
- run the
buildcommand inside the packagebackend-jsonrpc; - run the
buildandbuild:wasm-node-devcommands inside the packagejs-api(foldernpm/js-api); - run
pnpm iinside the packagejs-api(foldernpm/js-api), this will link the WebAssembly bindings and the JSON-RPC bindings;
The tests are run against the compiled files, which means that you need to run the
build command after you implemented features/bug fixes.
The Biome website is built with Astro. To start a development please check our README
For more information on how to help with translation, please see the translation contribution guidelines for our docs.
Internally, the Biome team adheres as closely as possible to the conventional commit specification. The following this convention encourages commit best-practices and facilitates commit-powered features like change log generation.
The following commit prefixes are supported:
feat:, a new featurefix:, a bugfixdocs:, a documentation updatetest:, a test updatechore:, project housekeepingperf:, project performancerefactor:, refactor of the code without change in functionality
Below are examples of well-formatted commits:
feat(compiler): implement parsing for new type of files
fix: fix nasty unhandled error
docs: fix link to website page
test(lint): add more cases to handle invalid rulesWhen creating a new pull request, it's preferable to use a conventional commit-formatted title, as this title will be used as the default commit message on the squashed commit after merging. See the dedicated section about conventional commit format.
Please use the template provided.
If the PR you're about to open is a bugfix/feature visible to Biome users, you CAN add a new bullet point to CHANGELOG.md. Although not required, we appreciate the effort.
At the top of the file you will see a Unreleased section.
The headings divide the sections by "scope"; you should be able to identify the scope that belongs to your change. If the change belongs to multiple scopes, you can copy the same sentence under those scopes.
Here's a sample of the headings:
## Unreleased
### Analyzer
### CLI
### Configuration
### Editors
### Formatter
### JavaScript APIs
### Linter
### ParserWhen you edit a blank section:
- If your PR adds a breaking change, create a new heading called
#### BREAKING CHANGESand add bullet point that explains the breaking changes; provide a migration path if possible. Read how we version Biome to determine if your change is breaking. A breaking change results in a major release. - If your PR adds a new feature, enhances an existing feature, or fixes a bug, create a new heading called
#### New features,#### Enhancements, or#### Bug fixes. Ultimately, add a bullet point that explains the change.
Make sure that the created subsections are ordered in the following order:
#### BREAKING CHANGES
#### New features
#### Enhancements
#### Bug fixesBecause the website displays the changelog, you should update the website using the following command:
just gen-web- Use the present tense, e.g. "Add new feature", "Fix edge case".
- If you fix a bug, please add the link to the issue, e.g. "Fix edge case #4444".
- You can add a mention
@userfor every contributor of the change. - Whenever applicable, add a code block to show your new changes. For example, for a new rule you might want to show an invalid case, for the formatter you might want to show how the new formatting changes, and so on.
If in doubt, take a look to existing changelog lines.
If your PR requires some update on the website (new features, breaking changes, etc.), you should create a new PR once the previous PR is successfully merged. When adding new features, the documentation should be part of a new PR, which will be merged right before the release.
We follow the specs suggested by the official documentation:
Odd minor versions are dedicated to pre-releases, e.g. *.5.* .
Even minor versions are dedicated to official releases, e.g. *.6.*.
When releasing a new version of a Biome, follow these steps:
-
Add a changelog entry for every Pull Request that lacks one. You can filter merged PRs that don't update the changelog. Read our guidelines for editing the changelog.
-
Based on the changelog, determine which version number to use. See our versioning guide for more details.
-
Rename
Unreleasedto<version> (iso-date)in the changelog. -
Update
versionin Biome'spackage.jsonif applicable. -
Update to the same
versionin all crates if you publish crates. (Cargo.tomlandcrates/**/Cargo.toml) -
Linter rules have a
versionmetadata directly defined in their implementation. This field is set tonextfor newly created rules. This field must be updated to the new version. Then executejust gen-lint. -
Update the website with the new version number:
BIOME_VERSION=<version> cargo codegen-website. This will also copy the configuration schema in the right place. -
Once the PR is merged, the CI will trigger the
Release: *workflows. Once these workflows finish compiling the final artefact, they need to be approved manually.
We have several resources explaining about Biome. They will help you understand the project and codebase.
- Rust Dublin October 2023 - Biome - YouTube
- Rome, a Modern Toolchain! by Emanuele Stoppa - GitNation
- How to create a lint rule in Biome
Members are listed in alphabetical order. Members are free to use the full name, GitHub handle, or any other nickname they wish to be addressed. Members are free to disclose their pronouns.