@webority/biome-config 0.38.0 → 0.40.0

package/README.md

@@ -46,6 +46,26 @@ fails every file in the repo at once, drowning any real violation (one repo's le
   static-list exceptions get a documented per-line `biome-ignore`.
 - **`noConsole`** off for `scripts/**` + `logger.js`; CSS/SCSS not linted; the icon
   module's mixed export allowed.
+- **`StyleSheet.absoluteFillObject`** is an error, through the `no-absolute-fill-object` plugin
+  (below).
+
+## Plugins (GritQL)
+
+The config ships lint plugins in `plugins/` and turns them on for every product that extends it:
+
+| Plugin | Fails on | Why |
+|---|---|---|
+| `no-absolute-fill-object` | `StyleSheet.absoluteFillObject` | React Native 0.86 removed it. It is `undefined`, and spreading it silently leaves the view in the layout flow. Use `StyleSheet.absoluteFill` (spread it or use it directly). |
+
+A plugin finding is an error, so `biome check` and `biome lint` fail on it.
+
+**Your `biome.json` must sit beside the `node_modules` that holds `@webority/biome-config`.** Biome
+resolves a plugin path against the folder of your own `biome.json`, not against this package, so the
+config names its plugins as `./node_modules/@webority/biome-config/plugins/…`. That is the normal layout
+for an app folder (`biome.json`, `package.json` and `node_modules` together). In any other layout Biome
+stops with `Cannot read file` for the plugin on every run, so a wrong layout is never silent; a
+workspace root that runs Biome adds `@webority/biome-config` to its own `devDependencies`. Needs
+`@biomejs/biome` 2.5 or newer (checked on 2.5.5 and 2.5.15).
 
 Product-specific one-offs (a bespoke file that co-exports, etc.) still use a local
 `overrides` entry or a documented inline `biome-ignore` in that product.

package/biome.jsonc

@@ -24,6 +24,12 @@
         "lineEnding": "lf",
         "useEditorconfig": false
     },
+    // GritQL lint plugins shipped in this package. Biome resolves a plugin path against the folder of
+    // the product's own biome.json, not against this file, so the path goes through node_modules:
+    // the product's biome.json must sit beside the node_modules that holds @webority/biome-config.
+    // A plugin that cannot be read fails every lint run, so a wrong layout is never silent.
+    // no-absolute-fill-object: StyleSheet.absoluteFillObject is gone in React Native 0.86 (undefined).
+    "plugins": ["./node_modules/@webority/biome-config/plugins/no-absolute-fill-object.grit"],
     "linter": {
         "enabled": true,
         "rules": {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@webority/biome-config",
-  "version": "0.38.0",
+  "version": "0.40.0",
   "description": "Shared Biome lint + format policy for Webority frontend products. Extend it from a product biome.json so every repo inherits one fleet-decided ruleset, bumped by version — no per-repo drift.",
   "license": "SEE LICENSE IN LICENSE",
   "publishConfig": {
@@ -8,10 +8,12 @@
     "registry": "https://registry.npmjs.org/"
   },
   "files": [
-    "biome.jsonc"
+    "biome.jsonc",
+    "plugins"
   ],
   "exports": {
     "./biome.jsonc": "./biome.jsonc",
+    "./plugins/*": "./plugins/*",
     "./package.json": "./package.json"
   },
   "main": "biome.jsonc",

package/plugins/no-absolute-fill-object.grit

@@ -0,0 +1,7 @@
+language js
+
+// React Native 0.86 removed StyleSheet.absoluteFillObject. Spreading the undefined it now returns
+// silently leaves the view in the layout flow, so the name is an error everywhere.
+`StyleSheet.absoluteFillObject` as $use where {
+    register_diagnostic(span=$use, message="StyleSheet.absoluteFillObject was removed in React Native 0.86 and is undefined. Use StyleSheet.absoluteFill (spread it or use it directly).", severity="error")
+}