Glenn Becker

Oh and no need to apologies for being new to Qwik. Qwik is so new we're all pretty new to it. 😆

Would the Context APIs (createContext, useContext, useContextProvider) work for you here? They're not publicly documented but you can see their usage in the ToDo starter. [Link](https://github.com/BuilderIO/qwik/tree/main/starters/apps/todo/src)

I like this idea. Seems like ```typescript preventDefault:event={(e: Event) => bool} ``` would be the most flexible? How do you feel about that option @youngboy?

The preventDefault type is defined by Qwik, so we can do whatever we want. 😆 Whether they merge it is a different story.

I think there would be implications for serialization, so there would need to be some investigating to see what the tradeoffs are or if this is a good idea.

Yeah, I'd be curious how much it adds to the Qwikloader size. I don't know if the simple rules are an issue for most use cases. I mean, as of...

Custom events? Although, I thunk the solution there should be more automatic than manual. https://github.com/BuilderIO/qwik/issues/786

I'm sure there can be improvements and more test cases. So, let me know what you find!

Glenn from Discord here. :wave: Looks like this might be a [vite thing](https://vitejs.dev/guide/features.html#css-pre-processors)? Does running `npm add -D sass` help?

Ah. Got it working by running that command and importing the styles in my layout instead of the root.tsx and using useStyles$ inside of the layout component. ``` import {...