feat: add MenuSeparator component

[alvaro-cuesta]

Extracted from this export:

function x(e) {
    const t = o.useContext(k).styles ?? v();
    return o.createElement("div", {
        className: t.ContextMenuSeparator
    })
}

It can be used as a child of Menu, i.e. sibling to MenuItem (see arrows in screenshot).

[PartyWumpus]

This is great, although I think we generally try and avoid matching on class names because valve is fickle and changes then often. Although looking at it I suppose you don't really have any other properties to match...
Maybe use findClass, should be slightly more stable?

[alvaro-cuesta]

@PartyWumpus thanks for looking into this!

Yeah, the component is pretty barebones and there's not a lot to match on 🫤 but I figured it was better to still extract the component rather than using the class manually in a div (in case Valve eventually changes the internal implementation, or adds some props to the component or whatever...)

Maybe use findClass, should be slightly more stable?

Can you elaborate further?

If I understand that correctly findClass gets a classnames module id and a classname on that module? The classnames module is exposed in gamepadContextMenuClasses but I'd still have to specify the classname literal, right? Isn't that the unstable part anyways?

Also, doesn't findClass return the post-bundled hashed classname? The component uses the pre-bundle classname anyways.

[PartyWumpus]

Also, doesn't findClass return the post-bundled hashed classname? The component uses the pre-bundle classname anyways.

Good point... Yeah this seems like the most reasonable way to match it then.