Alexandru Dima

@czb I agree. I explicitly tried to avoid any webpack assumptions in the `esm` distribution, that's why the `esm` distribution can be loaded by other loaders. But I could not...

@czb Yes, that is what I also do in the AMD loader I wrote 5 years ago :). But I don't want to do that in each and every JS...

@czb I am not familiar with the maze of github repositories used by whatwg or w3c nor their politics. I don't expect that `ECMA-262` (which standardises ECMAScript) would concern itself...

Thank you for the explanation @justinfagnani I'm going to think about this for a while, I was hoping to end up in a situation with the `/esm/` folder in our...

https://web.dev/css-module-scripts/ indicates a possible way forward: ```js import sheet from './styles.css' assert { type: 'css' }; document.adoptedStyleSheets = [sheet]; shadowRoot.adoptedStyleSheets = [sheet]; ``` or the async variant ```js const cssModule...

@spahnke Not sure I fully understand the problem. Here is what I get (which looks kind of OK): 

Might be related to #1199. But @spahnke AFAIK the flag `fixedOverflowWidgets` was never influencing the context menu (in any editor version).

@JounQin I'm sorry, I don't understand, what do you mean?

@JounQin I know what ESM is, I know what commonjs is, but I still don't understand what your issue is. Can you please provide clear steps, and then explain what...

Ok. I understand now. I don't believe that is a safe change. Here is what I have tried:  After applying that change, compiling and running `npm run test`, an...