Kendall Roth

I was able to get this to work (after changing an existing alias) **only** by rebuilding the `expo` cache with `expo r -c`.

Any update on this? I was a little confused about the comment regarding the `conf` library...does that mean it needs to be fixed in this library as well or is...

For some reason this is still happening on `[email protected]` while using `[email protected]`. P.S. Curious why it's mentioning `node_modules/src` when there is no `src` in the compiled `vuetify`... 🤷 ``` TypeError:...

Logging `typeof CSS` in the `vitest` setup file results in `object`, while checking for `typeof CSS.supports` results in `undefined`. If I add back the `global.CSS = {supports: () => false};`...

I _wonder_ if there is any relation to https://github.com/jsdom/jsdom/issues/2026, which indicates that some DOM libraries (`jsdom` in that case) do not support the `supports` property specifically? While I am using...

This can be achieved with a custom plugin, although I certainly agree that it would be amazing to have an actual sorting option (similar to operations and tags). ```ts const...

I also have noticed that adding global components that use `vue-property-decorator` will result in strange behaviour. In my case, the component is not included but simply rendered as a custom...

Is this related to #102 ? It is strange that this problem only occurs for globally registered components, but if necessary I can manually specify `name` in the `@Component` decorator......

Turns out that adding `removedClippedSubviews={false}` does resolve this issue! However, I would like to know why it actually happens without the prop change? Any input?

Also just started running into this, and am wondering if it's due to a different issue with `_ctypes` (not if the same in the above case though). I am using...