eslint-config-vylda-typescript 6.2.1 → 7.0.1

package/Changelog.md

@@ -4,6 +4,69 @@ All notable changes to this component will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [7.0.1] - 2026-09-21
+### Added
+- `ts` script (`tsc --noEmit --pretty`), a faster standalone type-check against the root `tsconfig.json` for use while iterating and in CI/pre-commit [Vilda Lipold]
+- `TConfig`, `TGetConfigOptions`, `TGetTsImportConfigOptions`, `TPlugin` and `TPlugins` types are now re-exported from the package entrypoint, documented in the README next to the rest of the public API [Vilda Lipold]
+### Changed
+- `lint` script now runs `npm run ts` before `eslint .`[Vilda Lipold]
+### Updated
+- Packages
+  - eslint (10.11.0)
+  - typescript-eslint (8.70.1)
+
+## [7.0.0] - 2026-09-20
+### Added
+- `importResolverAlias` option for `getConfig()` and `getImportConfig()` and `defaultImportResolverAlias` export, forwarded to vanilla for configuring path aliases (`@/...`); the aliased paths resolve with this package's TypeScript extensions, so `@/foo` finds `foo.ts` [Vilda Lipold]
+- `includeOffRules` option for `getImportConfig()`, defaulting to `true` [Vilda Lipold]
+- `off` config is now split into named per-category blocks (`typescript eslint/off/<category>`), and every rule in it documents the `@typescript-eslint` rule that replaces it or why no replacement is needed [Vilda Lipold]
+- `offImports` export with the `off` block for import rules, so it can be applied to TypeScript files only [Vilda Lipold]
+- Rules
+  - @typescript-eslint/no-generated-empty-object-type: error [Vilda Lipold]
+- Some colors in fix-extensions script for better visibility in the console [Vilda Lipold]
+- `vanillaBaseConfigs` export grouping the pure, unmodified vanilla rule-set configs under their original vanilla names [Vilda Lipold]
+### Changed
+- `eslint` moved from `dependencies` to `devDependencies`; the published package needs it only for types, so it no longer pulls a second copy of ESLint into consuming projects [Vilda Lipold]
+- `description` in `package.json` now matches the README [Vilda Lipold]
+- `@typescript-eslint/no-magic-numbers` options are read from vanilla's `no-magic-numbers` instead of a hardcoded copy that had drifted [Vilda Lipold]
+- Default `getConfig()` now also applies vanilla's `plus` rules to plain JS/CJS/MJS files, not just TypeScript files [Vilda Lipold]
+- `getConfig()` composes the vanilla rule sets in the same order as `eslint-config-vylda-vanilla` [Vilda Lipold]
+- Refactor to Typescript [Vilda Lipold]
+- Repository transfer to a new namespace [Vilda Lipold]
+- Rules
+  - `@typescript-eslint/prefer-nullish-coalescing` now ignores string primitives [Vilda Lipold]
+- Top-level rule-set exports (`base`, `bestPractices`, `errors`, `es6`, `plus`, `strict`, `stylistic`, `variables`) now combine the vanilla rules with this package's TypeScript updates and additions; use `vanillaBaseConfigs.<name>` for the untouched vanilla version [Vilda Lipold]
+- TypeScript import resolver is registered through `import-x/resolver-next` instead of the legacy `settings['import/resolver'].typescript` key, and is placed ahead of vanilla's node resolver, which stays as the fallback [Vilda Lipold]
+### Fixed
+- Rules
+  - `@stylistic/curly-newline` TypeScript enhancement (`TSModuleBlock`) moved into `plus.ts`, where it's defined together with the base rule instead of depending on config array order [Vilda Lipold]
+  - `@stylistic/lines-between-class-members` TypeScript enhancement (`exceptAfterOverload`) was never applied because it assumed a 2-element rule value while the base rule has 3; now handled independently of whether the exceptions object is present [Vilda Lipold]
+  - `@stylistic/object-curly-newline` TypeScript enhancements (`TSEnumBody`, `TSInterfaceBody`, `TSTypeLiteral`) were never applied because the rule was being read from the wrong base config [Vilda Lipold]
+  - `import-x/named` and `import-x/no-named-as-default-member` were disabled on plain JS/CJS/MJS files, where no TypeScript rule replaces them [Vilda Lipold]
+  - `no-shadow`, `no-undef`, `no-unused-vars` and `no-use-before-define` were disabled on plain JS/CJS/MJS files, where no TypeScript rule replaces them [Vilda Lipold]
+  - `off` rules for best practices were never applied, so 13 core rules kept reporting alongside their `@typescript-eslint` counterparts on TypeScript files [Vilda Lipold]
+### Removed
+- `getVanillaConfig`, an unused helper that had no consumer since the TypeScript migration [Vilda Lipold]
+- Packages
+  - @types/espree (espree 11 ships its own type definitions) [Vilda Lipold]
+  - tslib (unused; the build does not set `importHelpers`) [Vilda Lipold]
+- Rules
+  - @typescript-eslint/no-restricted-imports (deprecated since typescript-eslint 8.64.0; the core `no-restricted-imports` rule now applies as-is on both JavaScript and TypeScript files) [Vilda Lipold]
+  - @typescript-eslint/no-loop-func (deprecated since typescript-eslint 8.64.0; the core `no-loop-func` rule now applies as-is on both JavaScript and TypeScript files) [Vilda Lipold]
+### Updated
+- Packages
+  - @eslint/config-inspector (3.5.0) [Vilda Lipold]
+  - @types/node (24.13.5) [Vilda Lipold]
+  - eslint (10.10.0) [Vilda Lipold]
+  - eslint-config-vylda-vanilla package (6.0.0) [Vilda Lipold]
+  - eslint-import-resolver-typescript (4.4.5) [Vilda Lipold]
+  - typescript (6.0.3) [Vilda Lipold]
+  - typescript-eslint (8.70.0) [Vilda Lipold]
+### BREAKING
+- The `tsConfig` export is renamed to `tsConfigs`, for symmetry with `vanillaConfigs` and so it is not misread as the TypeScript compiler configuration. The old name is gone, not deprecated. [Vilda Lipold]
+- The `off` config now disables `import-x/named` and `import-x/no-named-as-default-member` instead of `import/named` and `import/no-named-as-default-member`, following vanilla's move from eslint-plugin-import to eslint-plugin-import-x. Anything that re-enabled, overrode or asserted on the old rule ids has to be renamed; left under the old name it is a no-op and the `import-x` rule keeps reporting on TypeScript files. [Vilda Lipold]
+- The TypeScript resolver can no longer be configured or overridden via raw `settings['import/resolver'].typescript` — `import-x/resolver-next` takes exclusive precedence over the legacy `import-x/resolver` / `import/resolver` settings keys, so anything set there is silently ignored. Pass `tsConfigPath` to `getImportConfig()` for the `project` option, and use the new `importResolverAlias` option for path aliases. [Vilda Lipold]
+
 ## [6.2.1] - 2026-01-23
 ### Fixed
 - readme file [Vilda Lipold]