You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@ljharb Haha, asking the question "Why is the cat burning?" I wasn't really looking for the answer "Well it's too late now", more for something like "It got to close to the oven" :)
There must be a reason why someone decided they didn't want it enabled by default (or at least I'd hope so). Just curious what that reason was/is
Also; Breaking change should always be possible with major version bump (if it's the right thing to do)
The reason is that that option didn't exist when the rule was created, and thus adding it later meant it couldn't be defaulted to "on" without being a breaking change.
It's certainly possible, but it's best to avoid breaking changes at all costs until they're absolutely necessary.
By default
import/no-useless-path-segments
only checksrequire
when the rule optioncommonjs
is set to true.Unfortunately this is not documented. Not sure where the best place for that to happen would be, so opening an issue.
Also, why is
require
not checked by default? It is somewhat cumbersome that one has to manually enable this setting.The text was updated successfully, but these errors were encountered: