Migrate renamed/removed preset names inside ignorePresets, not just extends

[tngwoerleij]

Tell us more.

Is your feature request related to a problem? Please describe

ExtendsMigration (lib/config/migrations/custom/extends-migration.ts) already rewrites preset names in extends when a preset has been renamed or removed, based on the removedPresets map in lib/config/presets/common.ts (and on the user-configured migratePresets option). However, there is no equivalent migration for ignorePresets.

This causes silent breakage when a preset used in ignorePresets gets renamed. For example, replacements:ojdbc10-to-ojdbc11 was renamed to replacements:ojdbc-to-ojdbc11:

removedPresets['replacements:ojdbc10-to-ojdbc11'] = 'replacements:ojdbc-to-ojdbc11';

Config that does:

{
  "extends": ["config:recommended"],
  "ignorePresets": ["replacements:ojdbc10-to-ojdbc11"]
}

gets the extends entries migrated correctly, but ignorePresets keeps the old, now-nonexistent preset name. Since the ignore list is matched by exact string against the resolved preset name (see shouldResolvePreset in lib/config/presets/index.ts), the entry silently stops matching anything — the preset is no longer ignored, and previously-suppressed config from the shared preset reappears without any warning or error.

Describe the solution you'd like

Extend the config migrations to also rewrite preset names inside ignorePresets, using the same rename/removal mapping (removedPresets + migratePresets) that ExtendsMigration already uses.

(This discussion post was created with the help of Claude)

[RahulGautamSingh]

Sounds good. PR Welcome