import.meta.webpackContext doesn't work if requiring inside npm packages

[Tofandel]

Bug report

What is the current behavior?
When requiring files using import.meta.webpackContext (added in #15446) that are located within a node_modules folder, eg:

const vuetify = import.meta.webpackContext('vuetify/lib/locale', {
  recursive: false,
  regExp: /(en|hu)\.js$/i,
});

It doesn't work properly and throws a warning during compilation

 WARNING  Compiled with 2 warnings                                                                                                                                                                                             6:40:36 PM

 warning  in ./node_modules/vuetify/lib/locale/ ./node_modules/vuetify/lib/locale/ sync nonrecursive (en%7Chu)\.js$/
 
Module not found: Error: Can't resolve 'webpack-meta-bug/node_modules/vuetify/lib/locale/vuetify/lib/locale/en.js' in 'webpack-meta-bug'

It seems to be adding the context path twice to the request

If the current behavior is a bug, please provide the steps to reproduce.
https://github.com/Tofandel/webpack-meta-bug

Use the following webpack config

const path = require('path')
module.exports = {
  resolve: {
    modules: [
      'node_modules',
      path.resolve(__dirname, './node_modules'),
    ]
  },
}

And use import.meta.webpackContext('some_package_files')

What is the expected behavior?
It should require the files correctly

Other relevant information:
webpack version: 5.70.0
Node.js version: 16.13.1
Operating System: WSL2 - Ubuntu 20.04
Additional tools:

[Tofandel]

Issue is happening there
https://github.com/webpack/webpack/blob/main/lib/dependencies/RequireContextPlugin.js#L132

[vankop]

you should remove several identical resolve.modules setting ( or in case of node_modules just remove this settings )

[vankop]

lets keep issue for now.. need to fix this anyway..

[Tofandel]

There is a fix #15581 ... It passes tests but the pipeline doesn't want to run on the PR

As for removing duplicate resolve.modules, that's the default of vue-cli, so not really an option given that the bug is indeed here, that was the whole point of this issue and fix in the first place, which took me hours to track down so I can imagine future users trying to use this in a vue project only to find the same bug, only to find after 2hours of debug and searching issues that the only workaround is to do

  chainWebpack: config => {
    config.resolve.modules.delete('node_modules');
  }

The problem is the resolution adds an item like
{context: 'node_modules/vuetify/lib/locales', request: 'vuetify/lib/locales/en.js' }

When it should be
{context: 'node_modules', request: 'vuetify/lib/locales/en.js' }

Or

{context: 'node_modules/vuetify/lib/locales', request: 'en.js' } (but this one breaks tests)