More permissive import/no-unassigned-import

[jamestalmage]

Currently, you can't do the following:

require('any-observable/register/zen');

I'm overriding the default rules as follows. I think it would make a sensible default:

{
	"import/no-unassigned-import": [
		"error",
		{
			"allow": [
				"@babel/polyfill",
				"**/register",
				"**/register/**"
			]
		}
	]
}

[sindresorhus]

Agreed. PR welcome.

[fregante]

Can/should this feature allow any import of packages that have polyfill in their names? Not just babel's

[sindresorhus]

@fregante Do you have any examples? The convention, except for Babel, is to use package-name/register, which we now support.

[fregante]

https://github.com/mozilla/webextension-polyfill

I guess /register is more common for node-native packages than web ones

[sindresorhus]

PR welcome if you care enough

[fregante]

I usually disable this rule completely because there are too many exceptions, I just thought Babel's could be made more generic

[sindresorhus]

What other exceptions have you encountered? I have honestly never encountered any time I needed to manually disable it.

[fregante]

Refined GitHub loads its features this way, so it’s disabled there. Many of my projects where “features” are self-contained files use unassigned imports. This isn’t something that can be whitelisted, it’s just at odds with the rule’s reasoning (which I assume is “modules shouldn’t have side effects”)