jase

Ideally the user gets a hint what he/she needs to do to fix this. Is this catchable on native side or is a change to the framework itself mandatory?

reason is that ```context.config.rootDir``` points to `nx-stencil-example\dist\libs\web-components` instead of `nx-stencil-example/libs/web-components/stencil.config.ts` So [resolving the paths injectGlobalPaths](https://github.com/ionic-team/stencil-sass/blob/b1cc372e98837f63d78b36226af072d083659fbc/src/util.ts#L44-L54) is errornous and causes an error on the dart sass package.

So what this global path does is just adding your globals to the head of each scss file with `@use myGlobal`. So the only workaround I can think of would...

Okay sounds like you had a different issue than me or did I break things working on master? In general the error message that is thrown on dart-sass is not...

Hey @adamdbradley, can you or someone else have a look for this PR? Thanks in advance

Different colors for different tags /scopes would already be great

Would be helpful for tools like nx

It is a fixed string like in the example. What do you mean with "ignore it"? eslint-disable-next-line? Is it necessary to analyze selector? Shouldn't it be enough to check if...

agree If clicking on Nominatim results you are getting a sidebar and a outline of your request on your mapview. Clicking on a result from "Internal" or "Geonames" does nothing...

Would be a great feature if custom options would be considered. https://developers.google.com/protocol-buffers/docs/proto#customoptions lists some usages on messages, fields, enums, services etc