[New] extensions: allow enforcement decision overrides based on specifier

[Xunnamius]

This PR implements in import/extensions: a new option enabling developers to override the decision to enforce or ignore extensions for imports with matching specifiers.

A demo package containing this feature is temporarily available for easy testing:

npm install --save-dev eslint-plugin-import@npm:@-xun/eslint-plugin-import-experimental

Prevent false negatives when checking the extensions of bespoke imports

I already use import/order with custom pathGroups. This allows me to control the grouping of certain paths, such as custom aliases from tsconfig.json's paths. This in turn ensures all imports are sorted properly, even when the project is using syntactically sound but otherwise bespoke custom aliases like my-project:api.js (in lieu of ../../../../src/api.js).

Unfortunately, if I mistype my-project:api (i.e. I forgot the extension), the import/extensions rule will still pass; the enforcement decision is "ignore" when it should have been "enforce". This is because, like import/order, the grouping strategy employed by this rule is quite coarse-grained, but unlike import/order, this rule is missing a pathGroups-like setting for finer-grained sorting. The goal of this PR is to fill that gap.

The documentation updates associated with the changes in this PR are part of a separate PR and can be previewed here (towards the bottom of the section). This PR also includes tests.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 95.61%. Comparing base (e5edf49) to head (63da958).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3105      +/-   ##
==========================================
+ Coverage   95.08%   95.61%   +0.53%     
==========================================
  Files          83       83              
  Lines        3618     3629      +11     
  Branches     1276     1282       +6     
==========================================
+ Hits         3440     3470      +30     
+ Misses        178      159      -19     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[ljharb]

What happens if two contradictory pathGroupOverrides options end up applying to the same file?

[Xunnamius]

What happens if two contradictory pathGroupOverrides options end up applying to the same file?

It mirrors the behavior of pathGroups from import/order: the first path group with a matching minimatch pattern wins.

[Xunnamius]

@ljharb Did this PR need any further work?

[ljharb]

@Xunnamius there's a few lines in the diff that aren't covered by tests.

[Xunnamius]

@ljharb I'm not seeing any uncovered lines on codecov? Though I did see some failing eslint tests. They are now passing.

It could be the case that I'm not seeing something obvious, so please let me know :)

[alexandre-le-borgne]

When can we expect this feature to be released?

[Xunnamius]

@alexandre-le-borgne Just a guess, but might be waiting on #3152, which I should find the time to finish up either today or tomorrow :)