Contribute to the library ​

There are several ways you can contribute to this project. You can contribute an avatar style or improve an existing one. Or you add tests or update the documentation.

Requirements ​

• A GitHub account
• Git installed (Learn how to install Git here)
• Node.js and NPM installed (Learn how to install Node.js here)

Set up project locally ​

1. Create a fork from the dicebear/dicebear repository.

2. Clone the project:

   git clone https://github.com/<YOUR_GITHUB_USERNAME>/dicebear.git

   git clone https://github.com/<YOUR_GITHUB_USERNAME>/dicebear.git

   If you've set up SSH, you can do this instead:

   git clone git@github.com:<YOUR_GITHUB_USERNAME>/dicebear.git

   git clone git@github.com:<YOUR_GITHUB_USERNAME>/dicebear.git

3. Install dependencies:

   cd dicebear
   npm install

   cd dicebear
   npm install

4. Create a build:

   npm run build

   npm run build

Contributing an avatar style ​

The Figma Exporter plugin is the easiest way to add an avatar style. Most avatar styles for DiceBear avatars were created this way. Alternatively, you can create an avatar style from scratch.

Place your avatar style in the following folder:

packages/@dicebear/<YOUR_AVATAR_STYLE_NAME>/

packages/@dicebear/<YOUR_AVATAR_STYLE_NAME>/

Note that your package name must be in the namespace @dicebear. You store the package name in the package.json of your avatar style.

{
  "name": "@dicebear/<YOUR_AVATAR_STYLE_NAME>"
  // ...
}

{
  "name": "@dicebear/<YOUR_AVATAR_STYLE_NAME>"
  // ...
}

Verifying your changes ​

You can test your new avatar style as follows:

npm install
npm run build --workspace @dicebear/<YOUR_AVATAR_STYLE_NAME>
npm run test --workspace @dicebear/<YOUR_AVATAR_STYLE_NAME>

npm install
npm run build --workspace @dicebear/<YOUR_AVATAR_STYLE_NAME>
npm run test --workspace @dicebear/<YOUR_AVATAR_STYLE_NAME>

The test (if set up correctly) creates multiple avatars under the path packages/@dicebear/<YOUR_AVATAR_STYLE_NAME>/tests/svg/ and checks that the result has not changed when the test is called again. It should not change because the creation with seed must be deterministic.

If you visually check the created avatars and find errors, you can correct your work and run the build and test again. But first delete the files in the directory.

Branching and committing ​

Once you are happy with the changes, create a branch so you can commit the changes.

git checkout -b <YOUR_AVATAR_STYLE_NAME>

git checkout -b <YOUR_AVATAR_STYLE_NAME>

Afterwards you have to add your changes to the stage and commit them.

git add .
git commit -m "Add: <YOUR_AVATAR_STYLE_NAME>"
git push origin <YOUR_AVATAR_STYLE_NAME>

git add .
git commit -m "Add: <YOUR_AVATAR_STYLE_NAME>"
git push origin <YOUR_AVATAR_STYLE_NAME>

Creating a Pull Request ​

Follow these instructions to create a Pull Request.

Contribute changes to an existing avatar style ​

Usually the official avatar styles were created with our Figma Exporter plugin. You can find the Figma source files in the src/index.ts file of the respective avatar style. So if you want to customize an avatar style, it's best to do the customization directly in Figma.

In order to edit the files in Figma, you must duplicate them. Otherwise, the steps are identical to those in Contributing an avatar style with the difference that you are working on an existing avatar style.

Contribute to a package ​

You want to contribute to a package, like @avatars/core or the official CLI? All packages are written in TypeScript and you can find them in the packages folder.

Verifying your changes ​

You can test your changes as follows:

npm install
npm run build --workspace <PACKAGE_NAME>
npm run test --workspace <PACKAGE_NAME>

npm install
npm run build --workspace <PACKAGE_NAME>
npm run test --workspace <PACKAGE_NAME>

If you are working on the CLI, you can test your changes after the build by calling the CLI script directly as follows:

node packages/dicebear/bin/index.js <COMMAND>

node packages/dicebear/bin/index.js <COMMAND>

Branching and committing ​

Once you are happy with the changes, create a branch so you can commit the changes.

git checkout -b <YOUR_BRANCH>

git checkout -b <YOUR_BRANCH>

Afterwards you have to add your changes to the stage and commit them.

git add .
git commit -m "Change: <YOUR_CHANGES>"
git push origin <YOUR_BRANCH>

git add .
git commit -m "Change: <YOUR_CHANGES>"
git push origin <YOUR_BRANCH>

Creating a Pull Request ​

Follow these instructions to create a Pull Request.

Branching and committing ​

Once you are happy with the changes, create a branch so you can commit the changes.

git checkout -b <YOUR_BRANCH>

git checkout -b <YOUR_BRANCH>

Afterwards you have to add your changes to the stage and commit them.

git add .
git commit -m "Change: <YOUR_CHANGES>"
git push origin <YOUR_BRANCH>

git add .
git commit -m "Change: <YOUR_CHANGES>"
git push origin <YOUR_BRANCH>

Creating a Pull Request ​

Follow these instructions to create a Pull Request.