path 'eslint/lib/util/glob-util' should be available until next major version

The version of ESLint you are using. v5.3.0

The problem you want to solve. The path eslint/lib/util/glob-util has been changed to eslint/lib/util/glob-utils with v5.3.0. This change can be considered a breaking change. Hence it should only be introduced with a new major version.

Your take on the correct solution to problem. Revert the renaming and hold it back until v6.0.0 gets released

Are you willing to submit a pull request to implement this change? Yes

[platinumazure]

@rfermann I found issue #11005; that issue was originally a feature request for a new CLI flag that exposes the glob utility method. The team consensus, as far as I can tell, seems to be that we don’t want to add a CLI option but we might be willing to expose it in CLIEngine. I believe exposing in CLIEngine would satisfy your use case as well.

To avoid confusion from the previous discussion in that issue, I would like to discuss further in a new issue. I’ll create a new issue with a concrete API proposal later today and I’ll link it here. If you think it will satisfy your use case, then you may wish to close this issue. Thanks for your patience as we try to figure out the best and most maintainable solution here!

[not-an-aardvark]

Fair enough. I still think we’ve clearly expressed the limits of our public API in our documentation, and our internal utility modules are not public. It’s unfortunate that the design of require allows access to package internals in cases like this (if there was a good way to make a package’s internal modules private, I’d be in favor of using it), but that doesn’t change the fact that this is a private API that shouldn’t be relied upon, and isn’t covered by semver.