@scayle/eslint-config-storefront 4.8.3-alpha.1 → 5.1.0

package/CHANGELOG.md

@@ -1,5 +1,122 @@
 # @aboutyou/eslint-config-sfc
 
+## 5.1.0
+
+### Minor Changes
+
+- `@scayle/eslint-config-storefront/v3` now wires an `eslint-import-resolver-typescript` resolver by default, pointed at the project's `tsconfig.json`. Path aliases like `@client/*` or `@server/*` resolve to real files, so `import-x/no-restricted-paths` and `import-x/no-cycle` see through them instead of only matching literal relative imports.
+
+  Two rules also newly cover ground they didn't before, both enabled for the first time rather than tightened:
+
+  - `import-x/order` wasn't configured anywhere in `/v3` until now. It ships at `error`, with an explicit `groups` option ranking aliased imports alongside package imports, ahead of relative ones. A project already using `/v3` may see new ordering errors on upgrade.
+  - `import-x/no-cycle` previously only saw `.js`/`.mjs`/`.cjs` files. `.ts` and `.tsx` are now included, so a circular dependency that only existed between TypeScript files, alias or not, is caught for the first time.
+
+  `resolver.tsconfigPath` points the resolver at a specific tsconfig, independent of `typescript.tsconfigPath` (which also switches on type-aware TypeScript rules). Without either set, the resolver and the `no-restricted-paths` zones fall back to resolving relative to ESLint's working directory, correct when linting runs via `pnpm lint`/CI but not guaranteed for an editor's ESLint extension. Set `resolver.tsconfigPath` to an absolute path if that matters for your setup.
+
+### Patch Changes
+
+- Added dependency `eslint-import-resolver-typescript@^4.4.5`
+
+## 5.0.0
+
+### Major Changes
+
+- Rebuilds the shared ESLint config directly on first-class plugins (`@eslint/js`, `typescript-eslint`, `eslint-plugin-n`, `eslint-plugin-jsonc`, `eslint-plugin-jsdoc`, `eslint-plugin-unicorn`, `eslint-plugin-regexp`, `@e18e/eslint-plugin`, `@eslint-community/eslint-plugin-eslint-comments`, `@vitest/eslint-plugin`) instead of wrapping `@antfu/eslint-config`. This drops the transitive dependency on framework-specific plugins (Vue, React, Astro, and others) this package never used, and makes every enabled rule visible directly in `config/`.
+
+  ## Breaking changes
+  - `eslintConfigStorefront({ isNuxt: true })` is replaced by a dedicated entry point: `import eslintConfigStorefrontNuxt from '@scayle/eslint-config-storefront/nuxt'`. `eslintConfigStorefront()` no longer accepts an `isNuxt` option. It always applies the framework-agnostic and JavaScript/TypeScript/JSDoc rule set.
+  - Rules keep each plugin's own published name instead of antfu's renamed aliases: `@typescript-eslint/*` (not `ts/*`), `vitest/*` (not `test/*` for Vitest-specific rules; `no-only-tests/*` is unchanged). Update any inline `eslint-disable` comment that references the old alias.
+  - `config/flat/` moved to `config/`. Flat config is the only supported mode, so the `flat/` segment was redundant. If your project imported anything from `@scayle/eslint-config-storefront/config/flat/*` directly, update the import path.
+  - `@typescript-eslint/consistent-type-imports` now allows `import('mod').Type` inline type annotations (`disallowTypeAnnotations: false`), matching common TypeScript usage the previous rule severity silently never reached under the old rule composition.
+  - The `eslint` peer dependency floor moves from `>=9.0.0` to `>=10.4.0`, matching what `eslint-plugin-unicorn@73` actually requires. An ESLint 9 project installed this package cleanly before but hit unmet peer warnings from the plugins themselves. Upgrade ESLint to 10.4 or later before upgrading this package.
+
+  ## New rule sets
+
+  Three additions widen the default coverage. Each is on by default in both `eslintConfigStorefront()` and `eslintConfigStorefrontNuxt()`, and each can surface new findings in an existing project on upgrade:
+
+  - **`eslint-plugin-unicorn`**: a curated subset of modernization rules (not the plugin's full `recommended` preset, which is hundreds of rules and largely stylistic). Covers things like preferring `node:`-prefixed core imports, `Array.isArray` over `instanceof Array`, and `Number.isNaN` over the global `isNaN`.
+  - **`eslint-plugin-regexp`**: the plugin's own `flat/recommended` preset. Flags unsafe or redundant regex patterns, including some that can cause catastrophic backtracking.
+  - **`@e18e/eslint-plugin`**: the [e18e](https://e18e.dev) community's `recommended` preset (modernization, module-replacement, and performance rules), with every rule downgraded to `warn`. The plugin is pre-1.0, and its rule set hasn't been reviewed against every consuming project yet, so findings surface without failing CI. Includes `ban-dependencies`, which flags known heavier packages with a lighter recommended alternative (for example `ora` in favor of `nanospinner`). Treat a `ban-dependencies` finding as a suggestion to evaluate, not a required change: swapping a dependency is a real decision with its own testing burden, not a lint fix.
+
+  ## Upgrading
+  1. Run `eslint .` after upgrading. Fix or explicitly suppress any new finding before merging.
+  2. If your project used `eslintConfigStorefront({ isNuxt: true })`, switch to the `/nuxt` entry point:
+
+     ```js
+     // Before
+     import eslintConfigStorefront from '@scayle/eslint-config-storefront'
+     export default eslintConfigStorefront({ isNuxt: true })
+
+     // After
+     import eslintConfigStorefrontNuxt from '@scayle/eslint-config-storefront/nuxt'
+     export default eslintConfigStorefrontNuxt()
+     ```
+
+  3. Search your project for any inline rule reference using an antfu alias (`ts/`, `test/` for Vitest rules) and update it to the plugin's real prefix (`@typescript-eslint/`, `vitest/`).
+
+- Adds `@scayle/eslint-config-storefront/v3`, a third entry point for the Storefront Application V3 stack (Hono, Inertia.js, Vue 3, not Nuxt). It builds on the default config and adds Vue language wiring, Vue rules, accessibility rules, `vue-i18n` linting, `@scayle/vue-composable` rules, Storybook file conventions, Tailwind CSS class validation, and `vue/block-order` enforcement.
+
+  ## Breaking changes
+  - The named exports `eslintConfigStorefront` and `eslintConfigStorefrontNuxt` are now `storefront` and `storefrontNuxt`. Neither name, nor the `./nuxt` entry point itself, shipped in a published release before this change, so this only affects code already on this pre-release. Default exports are unaffected:
+
+    ```js
+    // Before
+    import { eslintConfigStorefront } from '@scayle/eslint-config-storefront'
+
+    // After
+    import { storefront } from '@scayle/eslint-config-storefront'
+    ```
+
+  - `vue/block-order` is now enforced at error severity on `./v3`, with `template` before `script` before `style`. `eslint-plugin-vue`'s own `recommended` default only warns and defaults to script-first. Any `.vue` file with a script or style block ahead of its template now fails lint. Run `eslint --fix` to reorder them; the fix is purely mechanical and doesn't change behavior.
+
+  ## New entry point
+
+  `@scayle/eslint-config-storefront/v3` takes required `tailwind.entryPoint` and `i18n.localeDir` options, since the underlying plugins can't validate Tailwind classes or i18n keys without a real path. Optional options cover a shop's own custom elements, dynamically-used i18n keys, and fallthrough-attribute exceptions:
+
+  ```js
+  // eslint.config.mjs
+  import storefrontV3 from '@scayle/eslint-config-storefront/v3'
+
+  export default storefrontV3({
+    tailwind: {
+      entryPoint: './src/client/index.css',
+    },
+    i18n: {
+      localeDir: './src/i18n/locales/*.json',
+    },
+  })
+  ```
+
+  Named `v3`, not `vue`, since a future non-Vue Storefront Application V3 stack would extend this same entry point rather than needing a separate one.
+
+### Patch Changes
+
+- Added dependency `@e18e/eslint-plugin@^0.8.0`
+- Added dependency `@eslint-community/eslint-plugin-eslint-comments@^4.7.2`
+- Added dependency `@eslint/js@^10.0.0`
+- Added dependency `@intlify/eslint-plugin-vue-i18n@^4.5.1`
+- Added dependency `@scayle/eslint-plugin-vue-composable@workspace:*`
+- Added dependency `@vitest/eslint-plugin@^1.6.20`
+- Added dependency `eslint-plugin-better-tailwindcss@^4.7.0`
+- Added dependency `eslint-plugin-jsdoc@^64.2.1`
+- Added dependency `eslint-plugin-jsonc@^3.4.1`
+- Added dependency `eslint-plugin-n@^18.3.0`
+- Added dependency `eslint-plugin-no-only-tests@^3.4.0`
+- Added dependency `eslint-plugin-regexp@^3.2.0`
+- Added dependency `eslint-plugin-storybook@^10.5.8`
+- Added dependency `eslint-plugin-unicorn@^73.0.0`
+- Added dependency `eslint-plugin-vue@^10.10.0`
+- Added dependency `eslint-plugin-vuejs-accessibility@^2.6.0`
+- Added dependency `globals@^17.7.0`
+- Added dependency `vue-eslint-parser@^10.4.1`
+- Removed dependency `@antfu/eslint-config@^9.0.0`
+- Removed dependency `@eslint/eslintrc@^3.3.5`
+- Removed dependency `local-pkg@^1.2.1`
+- Updated dependency `eslint-config-flat-gitignore@^2.2.0` to `eslint-config-flat-gitignore@^2.3.0`
+- Updated dependency `eslint-plugin-import-x@^4.16.2` to `eslint-plugin-import-x@^4.17.1`
+- Updated dependency `eslint-plugin-sonarjs@^4.0.3` to `eslint-plugin-sonarjs@^4.2.0`
+- Updated dependency `typescript-eslint@8.67.0` to `typescript-eslint@^8.67.0`
+
 ## 4.8.3-alpha.1
 
 ### Patch Changes

package/README.md

@@ -3,11 +3,10 @@
 A [shared `eslint` config](https://eslint.org/docs/latest/extend/shareable-configs#creating-a-shareable-config) for SCAYLE Storefront projects and packages.
 Provides SCAYLE-specific `eslint` configuration for Frontend and Node.js projects using TypeScript.
 
-We migrated to `eslint@9` and [ESLint Flat config](https://eslint.org/docs/latest/use/configure/configuration-files), to provide improved organization and composition.
+Flat config only ([ESLint 10.4+](https://eslint.org/docs/latest/use/configure/configuration-files)). Built directly on first-class plugins (`@eslint/js`, `typescript-eslint`, `eslint-plugin-n`, `eslint-plugin-jsonc`, `eslint-plugin-jsdoc`, `eslint-plugin-unicorn`, `eslint-plugin-regexp`, `@e18e/eslint-plugin`, and others) with no shared-config aggregator dependency.
 
 Should you require support for `eslint@8`, please use `@scayle/eslint-config-storefront@3`.
 
-- Partially based on [@antfu/eslint-config](https://github.com/antfu/eslint-config)
 - [Official ESLint Documentation](https://eslint.org/docs/latest/)
 
 ---
@@ -24,11 +23,86 @@ And create a `eslint.config.mjs` in your project root:
 
 ```js
 // eslint.config.mjs
-import eslintConfigStorefront from '@scayle/eslint-config-storefront'
+import storefront from '@scayle/eslint-config-storefront'
 
-export default eslintConfigStorefront()
+export default storefront()
 ```
 
+### Nuxt projects
+
+Nuxt projects already get JavaScript, TypeScript, JSDoc, and import rules from
+[`@nuxt/eslint`](https://eslint.nuxt.com/). Use the `/nuxt` entry point instead, which
+only adds the framework-agnostic rules (comments hygiene, Node.js, JSON/JSONC, test-file
+conventions, SonarJS, Promise usage, modernization, and regex safety):
+
+```js
+// eslint.config.mjs
+import storefrontNuxt from '@scayle/eslint-config-storefront/nuxt'
+import withNuxt from './.nuxt/eslint.config.mjs'
+
+export default withNuxt(storefrontNuxt())
+```
+
+### Storefront Application V3 projects
+
+The Storefront Application V3 stack (Hono + Inertia.js + Vue 3, not Nuxt) should use the
+`/v3` entry point. It builds on the default config and adds Vue language wiring, Vue rules,
+accessibility rules, `vue-i18n` linting, `@scayle/vue-composable` rules, Storybook file
+conventions, Tailwind CSS class validation, and a TypeScript-aware import resolver:
+
+```js
+// eslint.config.mjs
+import storefrontV3 from '@scayle/eslint-config-storefront/v3'
+
+export default storefrontV3({
+  tailwind: {
+    entryPoint: './src/client/index.css',
+  },
+  i18n: {
+    localeDir: './src/i18n/locales/*.json',
+  },
+})
+```
+
+`tailwind.entryPoint` and `i18n.localeDir` are required, the underlying plugins can't
+validate Tailwind classes or i18n keys without a real path. Optional options:
+
+- `typescript.tsconfigPath`: absolute path to a `tsconfig.json`. Enables type-aware
+  TypeScript rules and points the import resolver at that file instead of
+  `<root>/tsconfig.json`
+- `resolver.tsconfigPath`: absolute path to a `tsconfig.json` for the import resolver only,
+  independent of `typescript.tsconfigPath`. Use this instead when you want the resolver
+  fix below without also switching on type-aware TypeScript rules
+- `i18n.messageSyntaxVersion`: `vue-i18n` message syntax version, defaults to `^11.2.8`
+- `i18n.unusedKeyIgnores`: regex-string patterns for translation keys used dynamically in code
+- `vue.undefComponentIgnores`: custom element (web component) tag names to exempt from `vue/no-undef-components`
+- `vueComposable.fallthroughAttrsIgnores`: path fragments to exempt from `require-explicit-fallthrough-attrs` (e.g. router-mounted page/layout roots that never receive fallthrough attributes)
+
+#### Import resolution
+
+`/v3` wires `eslint-import-resolver-typescript`, so `import-x` rules resolve `tsconfig.json`
+path aliases (`@client/*`, `@server/*`, or any other `paths` entry) to their real files
+instead of only matching literal relative imports. Three rules depend on that resolution
+to work correctly against an aliased import:
+
+- `import-x/no-restricted-paths`: zone violations across an alias fail lint, not just
+  across a relative path
+- `import-x/no-cycle`: circular dependencies through an aliased import are caught. `.vue`
+  files are the one exception, a cycle through a `.vue` file only surfaces when ESLint
+  lints that file directly
+- `import-x/order`: aliased imports rank alongside package imports (`external`), ahead of
+  relative ones, instead of dropping to last place once the resolver can see they resolve
+  to a project file
+
+Without `resolver.tsconfigPath` or `typescript.tsconfigPath` set, both the resolver and
+`import-x/no-restricted-paths`'s zones resolve relative to ESLint's own working directory.
+That's correct for `pnpm lint` and CI, since a monorepo's task runner always runs a
+package's lint script with that package as the working directory, but not guaranteed for
+an editor's ESLint extension, which can run with the workspace root as its working
+directory instead. Set `resolver.tsconfigPath` to an absolute path (for example,
+`new URL('./tsconfig.json', import.meta.url).pathname` in your `eslint.config.mjs`) if your
+editor's linting needs to match the command-line result.
+
 ### Add script for package.json
 
 For example:
@@ -77,66 +151,75 @@ Add the following settings to your `.vscode/settings.json`:
 
 ## Customization
 
-### Provides shared configurations
-
-#### Default config / `@scayle/eslint-config-storefront`
-
-Normally you only need to import the antfu preset:
+### Default config / `@scayle/eslint-config-storefront`
 
 ```js
 // eslint.config.mjs
-import eslintConfigStorefront from '@scayle/eslint-config-storefront'
+import storefront from '@scayle/eslint-config-storefront'
 
-export default eslintConfigStorefront()
+export default storefront({
+  typescript: {
+    // Enables type-aware rules for the given tsconfig
+    tsconfigPath: 'path/to/tsconfig.json',
+  },
+})
 ```
 
-### Extended Configuration
+### Nuxt config / `@scayle/eslint-config-storefront/nuxt`
 
 ```js
 // eslint.config.mjs
-import eslintConfigStorefront from '@scayle/eslint-config-storefront'
+import storefrontNuxt from '@scayle/eslint-config-storefront/nuxt'
 
-export default eslintConfigStorefront({
-  // If set to `true` removes all rule configurations
-  // that are provided by the `@nuxt/eslint` package
-  isNuxt: true, // Default via auto-detection of package `@nuxt/eslint`
+export default storefrontNuxt()
+```
 
-  // If set to `true` adds `eslint-plugin-tailwind`
-  isTailwind: true, // Default via auto-detection of package `eslint-plugin-tailwind`
+### Storefront Application V3 config / `@scayle/eslint-config-storefront/v3`
 
-  typescript: {
-    // Enables type-aware rules
-    // Only works if `isNuxt` is `false`!
-    // <https://github.com/antfu/eslint-config?tab=readme-ov-file#type-aware-rules>
-    tsconfigPath: 'path/to/tsconfig.ts',
-  },
-})
-```
+See [Storefront Application V3 projects](#storefront-application-v3-projects) above for the full option list.
+
+All three entry points return a [`FlatConfigComposer`](https://github.com/antfu/eslint-flat-config-utils),
+so you can chain `.append(...)`, `.prepend(...)`, `.override(...)`, or `.renamePlugins(...)` to layer
+project-specific rules on top.
+
+### Plugin names
 
-### Plugins Renaming
+Rules use each plugin's own published name (`@typescript-eslint/*`, `import-x/*`, `jsonc/*`,
+`jsdoc/*`, `node/*`, `promise/*`, `sonarjs/*`, `unicorn/*`, `regexp/*`, `e18e/*`, `vitest/*`,
+`eslint-comments/*`). There's no alias renaming. When you override or disable a rule inline,
+use that plugin's real prefix:
 
-Since flat config requires us to explicitly provide the plugin names (instead of the mandatory convention from npm package name), we renamed some plugins to make the overall scope more consistent and easier to write.
+```js
+// eslint-disable-next-line @typescript-eslint/consistent-type-definitions
+type Foo = { bar: 2 }
+```
 
-| New Prefix | Original Prefix        | Source Plugin                                                                              |
-| ---------- | ---------------------- | ------------------------------------------------------------------------------------------ |
-| `import/*` | `import-x/*`           | [eslint-plugin-import-x](https://github.com/un-es/eslint-plugin-import-x)                  |
-| `node/*`   | `n/*`                  | [eslint-plugin-n](https://github.com/eslint-community/eslint-plugin-n)                     |
-| `yaml/*`   | `yml/*`                | [eslint-plugin-yml](https://github.com/ota-meshi/eslint-plugin-yml)                        |
-| `ts/*`     | `@typescript-eslint/*` | [@typescript-eslint/eslint-plugin](https://github.com/typescript-eslint/typescript-eslint) |
-| `test/*`   | `vitest/*`             | [eslint-plugin-vitest](https://github.com/veritem/eslint-plugin-vitest)                    |
-| `test/*`   | `no-only-tests/*`      | [eslint-plugin-no-only-tests](https://github.com/levibuzolic/eslint-plugin-no-only-tests)  |
+### `e18e/*` rules ship as warnings
 
-When you want to override rules, or disable them inline, you need to update to the new prefix:
+The [e18e](https://e18e.dev) community's rule set (modernization, module-replacement, and
+performance rules) is enabled by default, but every `e18e/*` rule ships at `warn`, not `error`.
+The plugin is still pre-1.0, and its rule set hasn't been reviewed against every consuming
+project. A warning won't fail your build.
 
-```diff
--// eslint-disable-next-line @typescript-eslint/consistent-type-definitions
-+// eslint-disable-next-line ts/consistent-type-definitions
-type foo = { bar: 2 }
+One rule worth knowing about specifically: `e18e/ban-dependencies` flags a dependency in your
+project that has a lighter recommended alternative (for example `ora` in favor of
+`nanospinner`). Treat that finding as something to evaluate, not something to fix immediately.
+Swapping a dependency is a real decision with its own testing cost, not a lint fix. If you've
+decided to keep a flagged dependency, allowlist it explicitly rather than turning the rule off:
+
+```js
+export default storefront().append({
+  rules: {
+    'e18e/ban-dependencies': ['warn', { allowed: ['ora'] }],
+  },
+})
 ```
 
 ## View what rules are enabled
 
-[Anthony Fu](https://github.com/antfu) built a visual tool to help you view what rules are enabled in your project and apply them to what files, [@eslint/config-inspector](https://github.com/eslint/config-inspector).
+[@eslint/config-inspector](https://github.com/eslint/config-inspector) is a visual tool maintained
+by the ESLint core team to help you view what rules are enabled in your project and which files
+they apply to.
 
 Go into your project root that contains eslint.config.js and run:
 

package/config/ignores.mjs

@@ -0,0 +1,46 @@
+// Build artifacts, lockfiles, and tooling caches that no project should lint.
+export const GLOB_EXCLUDE = [
+  '**/node_modules',
+  '**/dist',
+  '**/package-lock.json',
+  '**/yarn.lock',
+  '**/pnpm-lock.yaml',
+  '**/bun.lockb',
+  '**/output',
+  '**/coverage',
+  '**/playwright-report',
+  '**/test-results',
+  '**/temp',
+  '**/.temp',
+  '**/tmp',
+  '**/.tmp',
+  '**/.history',
+  '**/.vitepress/cache',
+  '**/.nuxt',
+  '**/.next',
+  '**/.svelte-kit',
+  '**/.vercel',
+  '**/.changeset',
+  '**/.idea',
+  '**/.cache',
+  '**/.output',
+  '**/.vite-inspect',
+  '**/.yarn',
+  '**/CHANGELOG*.md',
+  '**/LICENSE*',
+  '**/*.min.*',
+  '**/__snapshots__',
+  '**/vite.config.*.timestamp-*',
+  '**/auto-import?(s).d.ts',
+  '**/components.d.ts',
+]
+
+/** @returns {import('eslint').Linter.Config[]} Flat config entries excluding build artifacts and tooling caches from linting. */
+export function ignoresConfig() {
+  return [
+    {
+      name: 'storefront/ignores',
+      ignores: GLOB_EXCLUDE,
+    },
+  ]
+}

package/config/index.mjs

@@ -0,0 +1,129 @@
+import { FlatConfigComposer } from 'eslint-flat-config-utils'
+import gitignore from 'eslint-config-flat-gitignore'
+import {
+  commentsConfig,
+  nodeConfig,
+  jsoncConfig,
+  sonarjsConfig,
+  promiseConfig,
+  importXConfig,
+  jsdocConfig,
+  regexpConfig,
+  e18eConfig,
+} from './rules.mjs'
+import { testConfig, GLOB_TESTS } from './test.mjs'
+import { ignoresConfig } from './ignores.mjs'
+import { javascriptConfig } from './javascript.mjs'
+import { typescriptConfig } from './typescript.mjs'
+import { unicornConfig } from './unicorn.mjs'
+
+/** @type {import('eslint').Linter.RuleEntry} */
+const CURLY_RULE = ['error', 'all']
+
+/** @type {import('eslint').Linter.RulesRecord} */
+const GLOBAL_RULES = {
+  curly: CURLY_RULE,
+  'node/prefer-global/process': 'off',
+}
+
+/** @type {import('eslint').Linter.RulesRecord} */
+const TEST_RULES = {
+  'no-console': 'off',
+  '@typescript-eslint/no-explicit-any': 'off',
+  'promise/avoid-new': 'off',
+}
+
+const IGNORE_PATTERNS = ['**/fixtures/**/*', '**/*.jsonc']
+
+/**
+ * @typedef {object} EslintConfigStorefrontOptions
+ * @property {object} [typescript] Options forwarded to `typescriptConfig`.
+ * @property {string} [typescript.tsconfigPath] Enables type-aware TypeScript rules when set.
+ */
+
+// Rules shared by every project regardless of framework: comments hygiene, Node.js,
+// JSON/JSONC, test-file conventions, SonarJS, Promise usage, modernization (unicorn,
+// e18e), and regex safety.
+function baseConfigs() {
+  return [
+    ...commentsConfig(),
+    ...nodeConfig(),
+    ...jsoncConfig(),
+    ...testConfig(),
+    ...sonarjsConfig(),
+    ...promiseConfig(),
+    ...unicornConfig(),
+    ...e18eConfig(),
+    ...regexpConfig(),
+  ]
+}
+
+// Global and test-file overrides. Flat config is last-match-wins, so these must be
+// appended after typescriptConfig() (and, on the base entry point, javascriptConfig()
+// and jsdocConfig()) on both entry points, not folded into baseConfigs(): otherwise a
+// rule these set (e.g. @typescript-eslint/no-explicit-any: 'off' for test files) gets
+// re-enabled by a later config with the same rule key for the same files.
+function overrideConfigs() {
+  return [
+    {
+      rules: GLOBAL_RULES,
+      ignores: [IGNORE_PATTERNS[0]],
+    },
+    {
+      files: GLOB_TESTS,
+      rules: TEST_RULES,
+    },
+    { ignores: [IGNORE_PATTERNS[1]] },
+  ]
+}
+
+/**
+ * Builds the SCAYLE Storefront ESLint flat config for a framework-agnostic or
+ * plain TypeScript project. Nuxt projects should use
+ * `@scayle/eslint-config-storefront/nuxt` instead, since `@nuxt/eslint` already
+ * covers JavaScript, TypeScript, JSDoc, and import rules.
+ *
+ * @param {EslintConfigStorefrontOptions} [config]
+ * @returns {FlatConfigComposer<import('eslint').Linter.Config, never>} Returns a FlatConfigComposer object to be consumed in projects eslint.config.mjs files
+ */
+export const storefront = function (config = {}) {
+  /** @type {FlatConfigComposer<import('eslint').Linter.Config, never>} */
+  const flatConfigComposer = new FlatConfigComposer()
+
+  const configs = [
+    ...baseConfigs(),
+    gitignore({ strict: false }),
+    ...ignoresConfig(),
+    ...importXConfig(),
+    ...javascriptConfig(),
+    ...typescriptConfig(config.typescript),
+    ...jsdocConfig(),
+    // Set tsconfigRootDir for all TypeScript files to support monorepo structure
+    // This ensures ESLint uses the correct tsconfig.json when multiple exist
+    {
+      files: ['**/*.mjs', '**/*.cjs', '**/*.ts', '**/*.tsx'],
+      languageOptions: {
+        parserOptions: {
+          tsconfigRootDir: process.cwd(),
+        },
+      },
+    },
+    ...overrideConfigs(),
+  ]
+
+  return flatConfigComposer.append(...configs)
+}
+
+/**
+ * Builds the SCAYLE Storefront ESLint flat config for a Nuxt project. Omits
+ * JavaScript, TypeScript, JSDoc, ignores, and import rules, since `@nuxt/eslint`
+ * already provides those for a Nuxt project.
+ *
+ * @returns {FlatConfigComposer<import('eslint').Linter.Config, never>} Returns a FlatConfigComposer object to be consumed in projects eslint.config.mjs files
+ */
+export const storefrontNuxt = function () {
+  /** @type {FlatConfigComposer<import('eslint').Linter.Config, never>} */
+  const flatConfigComposer = new FlatConfigComposer()
+
+  return flatConfigComposer.append(...baseConfigs(), ...overrideConfigs())
+}