Publish packages

Biome can resolve configurations and plugins from packages installed in node_modules/. This allows you to publish them once and reuse them across projects.

For Biome v2.6 and later, publish plugins and configurations through a manifest named biome-manifest.json or biome-manifest.jsonc.

A manifest can export plugin rules, rule presets, and configurations.

Publish Biome plugins

Publish Biome plugins as npm packages by declaring their rules and presets in a Biome manifest.

Export a local lint rule

Create biome-manifest.json in the root of your package. Set the required version field and add an empty plugins.rules array:
biome-manifest.json
```
1
{
2
  "version": 1,
3
  "plugins": {
4
    "rules": []
5
  }
6
}
```
Optionally, add the $schema field with the value ./node_modules/@biomejs/biome/manifest_schema.json to enable autocompletion and validation in editors.
Add a sample rule named useCompanyLogger by mapping its name to the GritQL file in plugins.rules:
biome-manifest.json
```
1
{
2
  "version": 1,
3
  "plugins": {
4
    "rules": [
5
      { "useCompanyLogger": "./rules/useCompanyLogger.grit" }
6
    ]
7
  }
8
}
```
The rules array accepts objects and strings. Use an object to map a rule name to a GritQL file in your package. Use a string to re-export a rule or preset from a dependency.

Add the manifest and rule files to the files field in package.json. Then add a biome entry to the exports field that maps to the manifest:

1
{
2
  "name": "@org/biome-plugins",
3
  "version": "1.0.0",
4
  "files": [
5
    "biome-manifest.json",
6
    "rules"
7
  ],
8
  "exports": {
9
    "biome": "./biome-manifest.json"
10
  }
11
}

Publish the package, then install @org/biome-plugins as a dependency of the consuming project. To enable a rule, add <PACKAGE_NAME>/<RULE_NAME> to plugins:
biome.json
```
1
{
2
  "plugins": ["@org/biome-plugins/useCompanyLogger"]
3
}
```

Export rule presets

Publish groups of related rules as presets by declaring them in a Biome manifest. Presets allow consumers to enable multiple rules together.

Add a plugins.presets field. This example defines recommended and strict presets:

1
{
2
  "version": 1,
3
  "plugins": {
4
    "rules": [
5
      { "useCompanyLogger": "./rules/useCompanyLogger.grit" },
6
      { "noLegacyLibrary": "./rules/noLegacyLibrary.grit" }
7
    ],
8
    "presets": {
9
      "recommended": ["useCompanyLogger"],
10
      "strict": ["useCompanyLogger", "noLegacyLibrary"]
11
    }
12
  }
13
}

To enable a preset, add <PACKAGE_NAME>/presets/<PRESET_NAME> to plugins. This example enables the recommended preset:
biome.json
```
1
{
2
  "plugins": ["@org/biome-plugins/presets/recommended"]
3
}
```

Re-export rules from another package

You can re-export rules from dependencies through your package.

The following example uses a hypothetical biome-ux-plugins package and re-exports its minimal preset and its noExternalLinks rule, which is not part of that preset.

Add biome-ux-plugins/noExternalLinks and biome-ux-plugins/presets/minimal to rules, then add biome-ux-plugins/noExternalLinks to the recommended preset:

1
{
2
  "version": 1,
3
  "plugins": {
4
    "rules": [
5
      "biome-ux-plugins/noExternalLinks",
6
      "biome-ux-plugins/presets/minimal",
7
      { "useCompanyLogger": "./rules/useCompanyLogger.grit" },
8
      { "noLegacyLibrary": "./rules/noLegacyLibrary.grit" }
9
    ],
10
    "presets": {
11
      "recommended": [
12
        "useCompanyLogger",
13
        "biome-ux-plugins/noExternalLinks"
14
      ],
15
      "strict": ["useCompanyLogger", "noLegacyLibrary"]
16
    }
17
  }
18
}

Consumers access re-exported rules through your package name. This keeps rule names and suppression comments stable if you replace the underlying rule.

The following configuration enables the package’s recommended preset and useAnimationFallback, a rule re-exported from biome-ux-plugins/presets/minimal:
biome.json
```
1
{
2
  "plugins": [
3
    "@org/biome-plugins/presets/recommended",
4
    "@org/biome-plugins/useAnimationFallback"
5
  ]
6
}
```

Publish Biome configurations

Publish configurations as npm packages by declaring them in a Biome manifest. To support consumers using a Biome version earlier than v2.6, use the legacy method.

Export multiple configurations

Create biome-manifest.json in the root of your package. Set the required version field and map each configuration name to its file in configs:
biome-manifest.json
```
1
{
2
  "version": 1,
3
  "configs": [
4
    { "recommended": "./configs/recommended.json" },
5
    { "strict": "./configs/strict.json" }
6
  ]
7
}
```
Optionally, add the $schema field with the value ./node_modules/@biomejs/biome/manifest_schema.json to enable autocompletion and validation in editors.

Add the manifest and configuration files to the files field in package.json. Then add a biome entry to the exports field that maps to the manifest:

1
{
2
  "name": "@org/biome-configs",
3
  "version": "1.0.0",
4
  "files": [
5
    "biome-manifest.json",
6
    "configs"
7
  ],
8
  "exports": {
9
    "biome": "./biome-manifest.json"
10
  }
11
}

Publish the package, then install @org/biome-configs as a dependency of the consuming project. To extend a configuration, add <PACKAGE_NAME>/configs/<CONFIG_NAME> to extends:
biome.json
```
1
{
2
  "extends": ["@org/biome-configs/configs/strict"]
3
}
```

Re-export configurations from another package

You can re-export configurations from dependencies through your package.

The following example uses the same hypothetical biome-ux-plugins package and re-exports its nuxt and astro configurations.

Add biome-ux-plugins/configs/nuxt and biome-ux-plugins/configs/astro to configs:

1
{
2
  "version": 1,
3
  "configs": [
4
    "biome-ux-plugins/configs/nuxt",
5
    "biome-ux-plugins/configs/astro",
6
    { "recommended": "./configs/recommended.json" },
7
    { "strict": "./configs/strict.json" }
8
  ]
9
}

Consumers access re-exported configurations through your package name. This keeps configuration references stable if you replace the underlying configuration.

In this example, the configurations from biome-ux-plugins are available under @org/biome-configs. To extend the nuxt configuration, add @org/biome-configs/configs/nuxt:
biome.json
```
1
{
2
  "extends": ["@org/biome-configs/configs/nuxt"]
3
}
```

Add a ./biome entry to the exports field that maps to the shared configuration. This example publishes @org/shared-configs/biome:
package.json
```
1
{
2
  "name": "@org/shared-configs",
3
  "type": "module",
4
  "exports": {
5
    "./biome": "./biome.json"
6
  }
7
}
```
Install @org/shared-configs in the consuming project, then add @org/shared-configs/biome to extends in biome.json:
biome.json
```
1
{
2
  "extends": ["@org/shared-configs/biome"]
3
}
```

Biome resolves @org/shared-configs from the working directory. For CLI commands, this is the directory where the command runs, usually the directory containing package.json. For the Biome Language Server, this is the project root.

Publish packages

Publish Biome plugins

Export a local lint rule

Export rule presets

Re-export rules from another package

Publish Biome configurations

Export multiple configurations

Re-export configurations from another package

Publish and share a configuration (legacy)