The documentation for prop:* states:
“Forces the prop to be treated as a property instead of an attribute.”
From what I can see you are using attribute semantics on a JavaScript property; that's not going to work.
#vite-plugin-solid errors when doing `prop:x` instead of `prop:x={bool}`
cinder heath
“I expect the JS property required of the component to be set to true.”
You are expecting attribute syntax to work where JS syntax is expected.
Editors are often only helpful but not necessarily correct.
What I would try is <some-component attr:required />. I'm not saying that it will work—that's just the next thing I would try.
JSX to WC interaction seems to hit a lot of weird edge cases.
cinder heath
I suspect that while there is an awareness of the issue, it would take somebody deeply steeped in the WC space who also uses Solid extensively to author competent and comprehensive documentation on the matter — individuals with that overlap are rare.
In the short term I'd stick to any info left behind by Joe Pea in connection with his work with lume.
But yeah, figuring out the JSX <-> WC dance can be annoying; I suspect that JSX being a to-JS DSL rather than actual HTML markup has a large part to do with it.