@devbie/style-guide 1.1.0 → 1.1.2

package/README.md

@@ -20,10 +20,12 @@ Single source of truth for code style across the devbie ecosystem
 | fewbie                                                                            | `frontend`   |
 | fewbie-starter, nightwatch-frontend                                                | `next`       |
 
-`next` is the `frontend` standard plus `eslint-config-next`, so Next.js
-applications and the rest of the frontend group never drift on the shared
-part. `eslint-config-next` requires the `next` package at load time, which is
-why repos without a Next runtime (fewbie) use `frontend` instead.
+`next` is the shared `core` baseline plus `eslint-config-next` (which already
+bundles the React / react-hooks / jsx-a11y layers), so every repo shares the
+same language-level rules while Next.js applications add only the canonical
+framework layer. `eslint-config-next` requires the `next` package at load
+time, which is why repos without a Next runtime (fewbie) use `frontend`
+instead.
 
 ## Usage
 
@@ -68,6 +70,14 @@ default, only as a deliberate milestone.
 
 ## Changelog
 
+- 1.1.2 — fix: `next` extends `core` plus the canonical Next rule set
+  (`eslint-config-next` already bundles React/react-hooks/jsx-a11y, so
+  spreading `frontend` on top redefined `jsx-a11y` and flat config rejected
+  it). The `frontend` React layer is now scoped to JSX/TSX files, so
+  non-React frontend repos (fewbie-cli) never evaluate React rules.
+- 1.1.1 — fix: `frontend` uses the flat variant of eslint-plugin-react-hooks
+  (`configs.flat["recommended-latest"]`); 1.1.0 shipped the legacy shape and
+  failed to load under flat config.
 - 1.1.0 — entries renamed to `backend` / `frontend` and layered: `core` is
   internal, `frontend` is framework-independent (React rules only), `next`
   adds the canonical Next.js rule set. `nest` was replaced by `backend`.

package/eslint/frontend.js

@@ -12,17 +12,20 @@ import jsxA11y from "eslint-plugin-jsx-a11y";
  * Deliberately independent of `eslint-config-next`: that package requires the
  * `next` package to be installed (its parser is `next/dist/compiled/babel
  * /eslint-parser`), while fewbie ships a Node CLI and has no Next runtime.
- * Next.js applications layer `@devbie/style-guide/eslint/next` on top of this
- * standard instead, so every frontend repo shares the same base rules.
+ * Next.js applications layer `@devbie/style-guide/eslint/next` on top instead.
  *
- * Repo-specific rules and ignores belong in the consumer's own
- * eslint.config.mjs, spread after this entry.
+ * The JSX/React layer is scoped to JSX/TSX files: repositories in the
+ * frontend group that carry no React code (fewbie-cli) receive the same
+ * standard without evaluating React rules at all.
  */
+const jsxFiles = ["**/*.jsx", "**/*.tsx"];
+const jsxOnly = (config) => ({ ...config, files: jsxFiles });
+
 export default [
   ...core,
-  react.configs.flat.recommended,
-  react.configs.flat["jsx-runtime"],
-  reactHooks.configs["recommended-latest"],
-  jsxA11y.flatConfigs.recommended,
+  jsxOnly(react.configs.flat.recommended),
+  jsxOnly(react.configs.flat["jsx-runtime"]),
+  jsxOnly(reactHooks.configs.flat["recommended-latest"]),
+  jsxOnly(jsxA11y.flatConfigs.recommended),
   prettierConfig,
 ];

package/eslint/next.js

@@ -1,19 +1,23 @@
 import { defineConfig, globalIgnores } from "eslint/config";
-import frontend from "./frontend.js";
+import core from "./core.js";
 import nextVitals from "eslint-config-next/core-web-vitals";
 import nextTs from "eslint-config-next/typescript";
 import prettierConfig from "eslint-config-prettier";
 
 /**
- * Next.js overlay for Next.js applications
+ * Next.js standard for Next.js applications
  * (nightwatch-frontend, fewbie-starter).
  *
- * It extends the shared frontend standard with the canonical Next rule set.
+ * Extends the shared `core` baseline with the canonical Next rule set.
+ * `eslint-config-next` already bundles the React / react-hooks / jsx-a11y
+ * layers, so the `frontend` React layer is not repeated here: spreading both
+ * would redefine the same plugin and flat config rejects that.
+ *
  * This entry can only be loaded where the `next` package is installed, which
  * is why frontend repos without a Next runtime use `frontend` instead.
  */
 export default defineConfig([
-  ...frontend,
+  ...core,
   ...nextVitals,
   ...nextTs,
   prettierConfig,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@devbie/style-guide",
-  "version": "1.1.0",
+  "version": "1.1.2",
   "description": "Single source of truth for devbie ecosystem code style: shared prettier config and eslint flat standards (backend, frontend, next)",
   "license": "MIT",
   "author": "worldzhy",