For maintainers only:

• This needs to be documented (issue in webpack/webpack.js.org will be filed when merged)
• This needs to be backported to webpack 4 (issue will be created when merged)

@vankop Thanks for your update.

I labeled the Pull Request so reviewers will review it again.

@sokra Please review the new changes.

I've created an issue to document this in webpack/webpack.js.org.

There seems to be a bug when using it with a package

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

First one works perfect, second one throws warning during compilation

 WARNING  Compiled with 2 warnings                                                                                                                                                                                             6:09:41 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 './node_modules/vuetify/lib/locale/vuetify/lib/locale/en.js' in '***'

 warning  in ./node_modules/vuetify/lib/locale/ ./node_modules/vuetify/lib/locale/ sync nonrecursive (en%7Chu)\.js$/

Module not found: Error: Can't resolve './node_modules/vuetify/lib/locale/vuetify/lib/locale/hu.js' in '***'

It seems to be using the context twice vuetify/lib/locale/vuetify/lib/locale/en.js instead of vuetify/lib/locale/en.js or am I missing something?

@Tofandel Looks like yes, please open an issue, thanks

Managed to get a minimal repro (funny enough only seems to happen with vue-cli, didn't happen with webpack-cli only) so something funny with the config is going on, so will open one

Got it to reproduce without vue-cli

Just adding this in the webpack config

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

Also, not really a bug, but just exploring this without a doc

I found that the default mode is sync and so if using chunkName without a mode it will have no effect, maybe we can change the default to 'lazy-once' if a chunkName is given? Otherwise I'd add a compilation warning if chunkName is given with a mode that doesn't use the chunkName

const vuetify = import.meta.webpackContext('vuetify/lib/locale', {
  recursive: false,
  chunkName: 'locales', // This does nothing until we add mode: 'lazy' or mode: 'lazy-once'
  regExp: /(en|hu)\.js$/i,
});

Also, not really a bug, but just exploring this without a doc

I found that the default mode is sync and so if using chunkName without a mode it will have no effect, maybe we can change the default to 'lazy-once' if a chunkName is given? Otherwise I'd add a compilation warning if chunkName is given with a mode that doesn't use the chunkName

const vuetify = import.meta.webpackContext('vuetify/lib/locale', {
  recursive: false,
  chunkName: 'locales', // This does nothing until we add mode: 'lazy' or mode: 'lazy-once'
  regExp: /(en|hu)\.js$/i,
});

yeah, need to add a warning if not lazy* mode