Rule `import/extensions` does not support dots in file names

[AntonioVentilii]

I have this rule set-up

	{
		files: ['src/frontend/src/**/*'],
		rules: {
			'import/extensions': [
				'error',
				{
					js: 'never'
				}
			]
		}
	},

But it wrongly raises these errors:

/Users/antonio.ventilii/projects/be-oisy-wallet/src/frontend/src/tests/utils/user-networks.test-utils.ts
  1:36  error  Unexpected use of file extension "env" for "$env/networks/networks.env"        import/extensions
  2:61  error  Unexpected use of file extension "store" for "$lib/stores/user-profile.store"  import/extensions
  4:33  error  Unexpected use of file extension "utils" for "$lib/utils/user-networks.utils"  import/extensions
  5:51  error  Unexpected use of file extension "mock" for "$tests/mocks/user-profile.mock"   import/extensions

Am I doing something wrong in the configs?

[AntonioVentilii]

I noticed that this was already raised twice:

• [import/extensions] Suffixes in file names #2147
• import/extensions does not like patterns with . in them #3109

It is not an uncommon pattern, it is quite common, widely used (as explained a few times in both the previous issues).

Shouldn't the rule support these cases? Why was it marked as unplanned (twice)?

[ljharb]

Not all that common, since it's only a handful of people that have had the issue in a decade.

It would be reasonable to try to come up with an option that could support this usage, I suppose.