Alex

@aslushnikov >Regarding the workaround, you can attach raw devtools protocol session with target.createCDPSession() and enable network domain manually there. It should give you some events. Could you elaborate on this:...

@alexander-akait What you mean by `import(..)`? What is the replacement for `require.context` in ESM? Here I found https://webpack.js.org/api/module-variables/#importmetawebpack I tried to use `import.meta.webpackContext` but got the error: `{}.webpackContext is not...

It turned out that this happens when `import.meta.webpackContext` is used inside `html-webpack-plugin` template module. ```js new HtmlWebpackPlugin({ filename: "index.html", template: "template.js", }), ``` and tempalte.js somethingn like (just for the...

@vankop hah that's funny, actually when I tried this in the code it was spelled correctly, I'm not sure why added `s` then. So the error with `import.meta.webpackContext` happens as...

> then you have loader that changes No. I've created a simple repro https://github.com/wclr/webpack-import-meta-context-issue

@alexander-akait > they execute template using Node.js, so you don't have webpackContext, But why if I use CJS module I can use `require.context` here?

@alexander-akait hah thanks! I just replaced `require.context` with `import.meta.webpackContext` and got call with 4 params: ``` const context = import.meta.webpackContext( "@charta/client/fonts/proxima", true, /^((?!(Thin)).)*$/, "sync" ) ``` And got this error....

@alexander-akait Yes I see this in docs)) it works ok now. It is just misleading webpack error.

It depends on your setup and what you are doing. I usually use yalc packages as workspaces with pnpm.

> Would enable cool stuff like post-processing of the vdom tree, for achieving overlay tutorials, skins, etc. This is just usual stuff what is wrong with it without `updateIn`?