@ololoepepe/eslint-config 0.1.0 → 0.1.2

package/CHANGELOG.md

@@ -4,6 +4,28 @@ All notable changes to this project are documented in this file. The format is
 based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and this
 project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.1.2] - 2026-07-02
+
+### Fixed
+
+- **base:** resolved a mutual exclusion between `unicorn/prefer-export-from` and
+  `no-duplicate-imports` ({`includeExports: true`}). A binding imported for
+  internal use **and** re-exported (`import {x} from './m'; ... use x ...;
+  export {x};`) had no valid arrangement: the former demanded `export…from`,
+  which the latter forbade, and the internal use blocked dropping the import.
+  `unicorn/prefer-export-from` is now configured with `{checkUsedVariables:
+  false}`, so it no longer rewrites re-exports of internally-used bindings; pure
+  re-exports are still pushed to `export…from`. Added regression tests covering
+  re-export compatibility.
+
+## [0.1.1] - 2026-06-30
+
+### Fixed
+
+- **react:** the `/react` layer now enforces **kebab-case filenames only**.
+  Previously it also allowed PascalCase (for component files); it now inherits
+  the base kebab-case rule.
+
 ## [0.1.0] - 2026-06-30
 
 A major modernization of the config. **This release contains breaking changes.**
@@ -49,4 +71,5 @@ A major modernization of the config. **This release contains breaking changes.**
 - JSX parsing in the base config: `@babel/eslint-parser@8` no longer enables JSX
   via `ecmaFeatures.jsx` alone; it now uses `babelOptions.parserOpts.plugins`.
 
+[0.1.1]: https://gitlab.void-walkers.com/libs/eslint-config/-/releases/v0.1.1
 [0.1.0]: https://gitlab.void-walkers.com/libs/eslint-config/-/releases/v0.1.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ololoepepe/eslint-config",
-  "version": "0.1.0",
+  "version": "0.1.2",
   "description": "ESLint config",
   "type": "module",
   "main": "src/index.js",

package/src/plugins/unicorn.js

@@ -213,7 +213,19 @@ export const rules = {
   'unicorn/prefer-else-if': 'error',
   'unicorn/prefer-error-is-error': 'off',
   'unicorn/prefer-event-target': 'error',
-  'unicorn/prefer-export-from': 'error',
+  'unicorn/prefer-export-from': [
+    'error',
+    {
+      // Do not require `export…from` for a binding that is also used internally:
+      // `import {x} from './m'; ... use x ...; export {x};`. With the default
+      // (checkUsedVariables: true) this pattern is unsatisfiable — the rule demands
+      // `export {x} from './m'`, but `no-duplicate-imports` ({includeExports: true})
+      // forbids importing and export-from'ing the same path, and the internal use
+      // means the import cannot be dropped. Pure re-exports (binding never used
+      // internally) are still required to use `export…from`.
+      checkUsedVariables: false
+    }
+  ],
   'unicorn/prefer-flat-math-min-max': 'error',
   'unicorn/prefer-get-or-insert-computed': 'error',
   'unicorn/prefer-global-number-constants': 'error',

package/src/react.js

@@ -27,15 +27,7 @@ export default [
     rules: {
       ...jsxStylisticRules,
       ...pluginReactRules,
-      ...pluginReactHooksRules,
-      // React components are conventionally PascalCase (e.g. `Button.jsx`), so
-      // allow it alongside the base kebab-case for non-component files.
-      'unicorn/filename-case': ['error', {
-        cases: {
-          kebabCase: true,
-          pascalCase: true
-        }
-      }]
+      ...pluginReactHooksRules
     },
     settings: {
       'react-x': {