Bug: `no-missing-require` does not work with `module-aliases`

[JesseDocken]

Environment

Node version: 20.18.1
npm version: 10.8.2
ESLint version: 9.26.0
eslint-plugin-n version: 17.19.0
Operating System: Ubuntu 22.04 WSL

What rule do you want to report?

no-missing-require

Link to Minimal Reproducible Example

https://eslint-online-playground.netlify.app/#eNptUtFOhDAQ/JVNX9DkON65mGjiX1hjKuw11bKt22IuIfy7La0nGl8W2M7szDJdROChw4uavMXjWxC9YPyYDeNNM7lxttgqa1ToGLUJEbm5PUmSNDgKERYIkWGFO7iS7l9VwC5iiC+FvyO4JGGdvkmk3BSHTVx5v8cXE/UdL95xDElgkSwJsl4PTYY3ubGeck2DMFhD8ZhUzkaXEcUi7czJCmu9nbWhlqQo5ooMjHhWs43wlJWWXAAKNPRpV4L1UJqcvOVW+QKQgjpy7WRCMKTbqidFn06Q2bEUBbrmRyrPZX2vhnel88qOkuNtnhSenWY1Vfo1Gik2dSlG/HxEjzQiDQZT/+rke8FCtSr/p0r7Odxt/y9qH/tvyGa+mqhpPWTUHw/bFSjMY1cTruSUmFi/ALB40kc=

What did you expect to happen?

The rule should be able to navigate over the aliases, or provide a mechanism to override how the paths are negotiated.

Participation

• I am willing to submit a pull request for this issue.

Additional comments

No response

[scagood]

I am not sure this is something we would want to support explicitly, I would suggest you look into the resolverConfig option.

You can see the full usage over at webpack/enhanced-resolve