@webority/biome-config 0.109.4 → 0.109.6
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +4 -2
- package/a11y.jsonc +1 -1
- package/biome.jsonc +2 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -20,7 +20,7 @@ bits — `vcs.root` and `files.includes`:
|
|
|
20
20
|
|
|
21
21
|
```jsonc
|
|
22
22
|
{
|
|
23
|
-
"$schema": "https://biomejs.dev/schemas/2.
|
|
23
|
+
"$schema": "https://biomejs.dev/schemas/2.6.4/schema.json",
|
|
24
24
|
"extends": ["@webority/biome-config/biome.jsonc"],
|
|
25
25
|
"vcs": { "enabled": true, "clientKind": "git", "useIgnoreFile": true, "root": ".." },
|
|
26
26
|
"files": {
|
|
@@ -82,7 +82,9 @@ config names its plugins as `./node_modules/@webority/biome-config/plugins/…`.
|
|
|
82
82
|
for an app folder (`biome.json`, `package.json` and `node_modules` together). In any other layout Biome
|
|
83
83
|
stops with `Cannot read file` for the plugin on every run, so a wrong layout is never silent; a
|
|
84
84
|
workspace root that runs Biome adds `@webority/biome-config` to its own `devDependencies`. Needs
|
|
85
|
-
`@biomejs/biome` 2.5 or newer (checked on 2.5.
|
|
85
|
+
`@biomejs/biome` 2.5 or newer (checked on 2.5.15 and 2.6.4). The shared files carry no `$schema`, because
|
|
86
|
+
Biome refuses an extended config whose schema names a different Biome version; your own `biome.json` names
|
|
87
|
+
the schema of the Biome version you install.
|
|
86
88
|
|
|
87
89
|
Product-specific one-offs (a bespoke file that co-exports, etc.) still use a local
|
|
88
90
|
`overrides` entry or a documented inline `biome-ignore` in that product.
|
package/a11y.jsonc
CHANGED
|
@@ -1,5 +1,5 @@
|
|
|
1
1
|
{
|
|
2
|
-
"$schema"
|
|
2
|
+
// No "$schema" here, for the reason biome.jsonc gives.
|
|
3
3
|
// Opt-in accessibility checks. A product extends this file after biome.jsonc to turn the a11y group on:
|
|
4
4
|
// "extends": ["@webority/biome-config/biome.jsonc", "@webority/biome-config/a11y.jsonc"]
|
|
5
5
|
"root": false,
|
package/biome.jsonc
CHANGED
|
@@ -1,5 +1,6 @@
|
|
|
1
1
|
{
|
|
2
|
-
"$schema":
|
|
2
|
+
// No "$schema" here on purpose: Biome refuses an extended config whose schema names a different Biome
|
|
3
|
+
// version, so a pinned schema would tie every product to that exact release.
|
|
3
4
|
// Not a standalone root config — it exists only to be `extends`-ed by a product's
|
|
4
5
|
// biome.json (which is the root). `root: false` stops Biome treating it as a nested
|
|
5
6
|
// competing root inside the monorepo that ships it.
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@webority/biome-config",
|
|
3
|
-
"version": "0.109.
|
|
3
|
+
"version": "0.109.6",
|
|
4
4
|
"description": "Shared Biome lint + format policy for Webority frontend products. Extend it from a product biome.json so every repo inherits one shared ruleset, bumped by version — no per-repo drift.",
|
|
5
5
|
"license": "SEE LICENSE IN LICENSE",
|
|
6
6
|
"publishConfig": {
|