Ari Kornfeld

I just want to say it more directly: this issue should be classified as a `bug`, not a feature request -- see my explanation in the previous two comments. (Consequently,...

@Julusian, I am wondering if the only place this matters is in Trigger conditions? - In actions, the expression is evaluated each time it's encountered. (Make a button to set...

I just realized that my comment about feedback isn't entirely correct: An example of a reasonable use that would be affected by the update question might be to trigger after...

@alexander-akait thank you for the reply. I realize that I cover several aspects of the problem in my original comment, but the code example referenced above uses `import.meta.dirname`. Please try...

Oh, and just to be clear, removing `node.__dirname` and `node.__filename` options has no effect. I added them after the original error in a failed attempt to fix the problem --...

@alexander-akait: (a) I am trying to do use `module.parser.javascript.importMeta: false`, so shouldn't that disable all `import.meta` processing anyway? (b) the reason I need to disable it is that it's producing...

@alexander-akait thank you for your timely replies. Please bear with me here: 1. I ran `yarn add webpack@webpack/webpack#main --dev` (and yarn install), commented out the node options and reran my...

OK, just to be super-careful. I changed the string in package.json in my wptest repo to exactly what you wrote, i.e. ~~~ "webpack": "git+https://github.com/webpack/webpack.git#main", ~~~ It didn't cause yarn to...

@alexander-akait wrote: >Oh, I see your problem, it is due devtool: 'eval-source-map' Thank you Alexander, that helps! So importMeta:false works as long as I don't use `devtool: 'eval-source-map'` or `devtool:...

Thank you @hai-x, for that awesome and precise diagnosis and explanation!!! I will need a little more time to confirm that everything else will work, but I am "cautiously optimistic"...