@rtorcato/repo-tooling 3.7.2 → 3.7.4

package/README.md

@@ -53,6 +53,20 @@ npx @rtorcato/repo-tooling copy oxlint       # → .oxlintrc.json
 npx @rtorcato/repo-tooling copy claude-skill # → .claude/skills/repo-tooling.md
 ```
 
+The Biome preset honours your `.gitignore`, so build output stays unlinted. One
+known gap: Biome cannot parse Tailwind CSS v4 stylesheets (`@theme`, `@source`,
+`@custom-variant`, `@apply`) and reports a parse error on them. If you use
+Tailwind v4, exclude your stylesheet in `biome.json`:
+
+```jsonc
+{
+  "extends": ["@rtorcato/repo-tooling/biome"],
+  // `includes` replaces the preset's list rather than extending it — restate
+  // the exclusions you still want alongside the CSS one.
+  "files": { "includes": ["**", "!**/node_modules", "!**/dist", "!**/*.css"] }
+}
+```
+
 **Already have a project?** Don't rerun `setup` — use `doctor` + `fix`:
 
 ```bash

package/dist/cli/commands/setup-presets.js

@@ -1,4 +1,5 @@
 import { swiftFileList } from '../../languages/swift/scaffold.js';
+import { BIOME_CONFIG } from '../generators/linting.js';
 export const PRESET_NAMES = [
     'library',
     'web-app',
@@ -212,7 +213,7 @@ export function computeFileList(config) {
         files.push('tsconfig.json', 'reset.d.ts');
     }
     if (config.linting.tool === 'biome' || config.linting.tool === 'both') {
-        files.push('biome.jsonc');
+        files.push(BIOME_CONFIG);
     }
     if (config.linting.tool === 'eslint' || config.linting.tool === 'both') {
         files.push('eslint.config.mjs');

package/dist/cli/generators/linting.js

@@ -20,22 +20,79 @@ export async function generateLintingConfigs(config, targetDir) {
 }
 export async function generateOxlintConfig(targetDir) {
     // Oxlint's `extends` resolution from npm packages isn't reliably supported,
-    // so we copy the full preset rather than write a thin pointer file (same
-    // pattern as biome.jsonc — the user owns the file once it's in their repo).
+    // so we copy the full preset rather than write a thin pointer file.
     const { copyPreset } = await import('../utils/copy-preset.js');
     await copyPreset('oxlint', targetDir);
 }
+/** The one Biome config filename every code path writes. See BIOME_LEGACY_CONFIG. */
+export const BIOME_CONFIG = 'biome.json';
+/**
+ * The name this generator used to write. Biome resolves `biome.json` first and
+ * says nothing about a `biome.jsonc` sitting next to it, so a repo that had run
+ * both `fix biome` (biome.json) and `fix --resync` (biome.jsonc) ended up with
+ * two configs, one of them silently dead (#365). Both paths now write
+ * BIOME_CONFIG and delete this on the way past, so the ambiguity can't persist.
+ */
+export const BIOME_LEGACY_CONFIG = 'biome.jsonc';
+/**
+ * Used when nothing in the target repo says which Biome will read the config —
+ * a bare directory mid-`setup`, before `pnpm install` has run. Matches the
+ * `$schema` the shipped preset carries.
+ */
+const BIOME_SCHEMA_FALLBACK = '2.5.0';
+async function readJsonOrNull(filepath) {
+    try {
+        return (await fs.readJson(filepath));
+    }
+    catch {
+        return null;
+    }
+}
+/**
+ * The Biome version the scaffolded `$schema` URL should name (#363).
+ *
+ * A hardcoded version drifts the moment the consumer's Biome moves, and Biome
+ * reports the mismatch on *every* invocation ("The configuration schema version
+ * does not match the CLI version 2.5.7") — noise on a file the consumer never
+ * wrote. The installed package wins because it is literally the binary that
+ * will parse the file and emit that warning; the declared range is the next
+ * best statement of intent when node_modules isn't populated yet.
+ */
+export async function resolveBiomeSchemaVersion(targetDir) {
+    const installed = await readJsonOrNull(path.join(targetDir, 'node_modules', '@biomejs', 'biome', 'package.json'));
+    const pkg = await readJsonOrNull(path.join(targetDir, 'package.json'));
+    const deps = {
+        ...(pkg?.dependencies ?? {}),
+        ...(pkg?.devDependencies ?? {}),
+    };
+    // Both an exact version ("2.5.7") and a range ("^2.5.0") carry the x.y.z we
+    // need, so one pattern covers every source.
+    for (const candidate of [installed?.version, deps['@biomejs/biome']]) {
+        const match = typeof candidate === 'string' ? /(\d+\.\d+\.\d+)/.exec(candidate) : null;
+        if (match?.[1])
+            return match[1];
+    }
+    return BIOME_SCHEMA_FALLBACK;
+}
+/**
+ * The thin pointer config — the same shape this repo dogfoods. `fix biome` used
+ * to copy the whole preset inline instead, which meant the scaffolded file
+ * carried no `@rtorcato/repo-tooling/biome` reference for doctor's Biome check
+ * to match, and preset improvements never reached consumers.
+ */
 export async function generateBiomeConfig(targetDir) {
-    const biomeConfigPath = path.join(targetDir, 'biome.jsonc');
     // Biome 2.x schema + shape. The base preset (extends) already defines the
     // file globs via `files.includes`; emitting the old 1.x `include`/`ignore`
     // keys here forced consumers to run `biome migrate` before `biome check`
     // would run at all.
+    const version = await resolveBiomeSchemaVersion(targetDir);
     const biomeConfig = {
-        $schema: 'https://biomejs.dev/schemas/2.5.0/schema.json',
+        $schema: `https://biomejs.dev/schemas/${version}/schema.json`,
         extends: ['@rtorcato/repo-tooling/biome'],
     };
-    await fs.writeJson(biomeConfigPath, biomeConfig, { spaces: 2 });
+    await fs.writeJson(path.join(targetDir, BIOME_CONFIG), biomeConfig, { spaces: 2 });
+    await fs.remove(path.join(targetDir, BIOME_LEGACY_CONFIG));
+    return BIOME_CONFIG;
 }
 export async function generateESLintConfig(config, targetDir) {
     const eslintConfigPath = path.join(targetDir, 'eslint.config.mjs');

package/dist/cli/generators/readme.js

@@ -51,7 +51,7 @@ ${config.testing.framework !== 'none' ? '├── tests/              # Test fi
 ├── dist/               # Build output${config.projectType === 'library' ? ' (library)' : ''}
 ├── package.json
 ${config.typescript.enabled ? '├── tsconfig.json        # TypeScript configuration' : ''}
-${config.linting.tool === 'biome' || config.linting.tool === 'both' ? '├── biome.jsonc          # Biome configuration' : ''}
+${config.linting.tool === 'biome' || config.linting.tool === 'both' ? '├── biome.json           # Biome configuration' : ''}
 ${config.linting.tool === 'eslint' || config.linting.tool === 'both' ? '├── eslint.config.mjs    # ESLint configuration' : ''}
 ${config.linting.tool === 'eslint' ? '├── prettier.config.mjs  # Prettier configuration' : ''}
 ${config.testing.framework === 'vitest' ? '├── vitest.config.ts     # Vitest configuration' : ''}

package/dist/languages/js/checks.js

@@ -56,7 +56,9 @@ export const FILE_CHECKS = [
         expected: `extends "${PACKAGE}/biome"`,
         matcher: /@rtorcato\/(?:js|repo)-tooling\/biome/,
         optional: true,
-        hint: 'Run `npx @rtorcato/repo-tooling copy biome` to scaffold',
+        // `fix biome`, not `copy biome`: copy drops the whole preset inline, which
+        // carries no `extends` for the matcher above to find (#365).
+        hint: 'Run `npx @rtorcato/repo-tooling fix biome` to scaffold',
     },
     {
         check: 'ESLint',

package/dist/languages/js/fixers.js

@@ -7,7 +7,7 @@ import { generateHuskyConfig, generatePrePushHook } from '../../cli/generators/g
 import { CI_WORKFLOW, generateGitHubActions } from '../../cli/generators/github-actions.js';
 import { generateGitLabCI } from '../../cli/generators/gitlab-ci.js';
 import { GH_WORKFLOWS, generateGhWorkflow } from '../../cli/generators/github-workflows.js';
-import { generateESLintConfig, generatePrettierConfig } from '../../cli/generators/linting.js';
+import { BIOME_CONFIG, generateBiomeConfig, generateESLintConfig, generatePrettierConfig, } from '../../cli/generators/linting.js';
 import { alignNodeVersion, ensureEnginesNode, ensurePackageManager, generateKnipConfig, generateNvmrc, generateSizeLimitConfig, generateVscodeExtensions, } from '../../cli/generators/misc.js';
 import { scriptsOf } from './ci.js';
 import { composeVerifyScriptFromPkg, ensureScripts } from '../../cli/generators/package-json.js';
@@ -122,13 +122,15 @@ const GH_WORKFLOW_FIXERS = GH_WORKFLOWS.map((name) => ({
 export const FIXERS = [
     {
         target: 'biome',
-        description: 'Scaffold biome.json extending the @rtorcato/repo-tooling preset, plus the scripts that run it',
+        description: `Scaffold ${BIOME_CONFIG} extending the @rtorcato/repo-tooling preset, plus the scripts that run it`,
         appliesTo: ['Biome'],
-        outputs: ['biome.json', 'package.json (scripts)'],
+        outputs: [BIOME_CONFIG, 'package.json (scripts)'],
         canFixDrift: true,
         async run({ targetDir }) {
-            const result = await copyPreset('biome', targetDir);
-            const filesWritten = [result.target];
+            // Shares generateBiomeConfig with the setup/resync path — the two used to
+            // scaffold different filenames with different contents (#365).
+            const written = await generateBiomeConfig(targetDir);
+            const filesWritten = [written];
             // A config with no way to run it left `pnpm check` undefined, which the
             // generated CI called and `fix verify` needed to compose a chain (#364).
             if (await ensureScripts(targetDir, BIOME_SCRIPTS))

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@rtorcato/repo-tooling",
-	"version": "3.7.2",
+	"version": "3.7.4",
 	"description": "One CLI to scaffold, audit and fix your repo's whole toolchain — linting, tests, commits, releases & CI.",
 	"type": "module",
 	"keywords": [

package/tooling/biome/biome.json

@@ -1,7 +1,7 @@
 {
 	"$schema": "https://biomejs.dev/schemas/2.5.0/schema.json",
 	"vcs": {
-		"enabled": false,
+		"enabled": true,
 		"clientKind": "git",
 		"useIgnoreFile": true
 	},