Dale Sande

I also have this issue. I am considering BackstopJS for the Auro design system using shadow DOM custom elements. When trying to use a selector ID of an element within...

> E.g. if you are using playwright engine That was the tipoff. Moving to PlayWright allows me to select elements in the shadowDOM without any additional configuration.

To see a setup that is working with the shadow DOM and PlayWright, see https://github.com/AlaskaAirlines/auro-input/pull/104

> I kind of like that the npm page show the readme with the rules, so I'm not sure if I agree about the improvement, but I'm open to hear...

I will throw in a personal agenda as well. I am building a design system and part of that is using tools like yours to maintain quality. I'd like to...

> @blackfalcon the list of _available_ rules in the plugin does not mean that this is the list of rules applied in your design system. And each rule is already...

Wow ... 2019 and this is still an issue?

I went down the route of updating the transformGroup, but really wanted to point out that there is an issue with expected default behavior.

Running SSR build with Svelte/Vite ``` (node:29857) Warning: To load an ES module, set "type": "module" in the package.json or use the .mjs extension. (Use `node --trace-warnings ...` to show...

> Two years on and nothing on proper ESM support tells me this is a dead end project and I need to migrate my code to another library. ESM is...