Martijn Saly

Okay. From the documentation, I would have **never** known to use `selector-unify` for this. It's unclear to me what that actually does under the bonnet. And trying out your example...

> selector-unify(), like all Sass functions, is documented on the functions page. As the docs say, it returns "a single selector that matches only elements matched by both input selectors"....

Here's another proof: ``` globals: { '@vue/vue2-jest': { templateCompiler: { get compiler() { console.log('getting compiler'); return VueTemplateBabelCompiler; } } } } ``` It does spew out `getting compiler` a dozen...

Digging into the source, something along the way is DELETING the `compiler` option from the `config` object. Why?! Also it searches for `globals['vue-jest']` which makes the documentation as incorrect as...

I worked around it, but I'm sorry I don't remember how. I was on the clock, and didn't have time to post my workaround.

Found why this is happening. Angular-trix doesn't require trix. Doesn't support any type of AMD system at all. That explains. Too bad it doesn't say anything about trix.js not being...

I already did that kind of research 😉 VScode is showing a notification in the bottom-right that says `Getting code action from "ESLint"` so it's quite definitely not another extension...

> so I might move this issue to discussions instead That's fine. I'm not used to discussions being a thing yet, so I go to issues mainly out of habit....

I figured if I'm spending 2 hours gettings this to work, I might as well share it 😀

> > > Thank you for bug report. The incident is same as [the previous one](https://github.com/Yutaka-Sawada/MultiPar/issues/19). Because I cannot test the behavior myself, I didn't not solve this issue. I...