Problem importing raw css into ShadowDom about fable.lit HOT 6 OPEN

Can you share how are you using the component?

LitElement.init must be called on top of the render function this error if I recall correctly only happens if you don't call it in the top of your LitElement decorated function so if we could see how you were using it on your first example it would be nice

Also I would test this in the final build mode because I'm not sure it is supported

from fable.lit.

Here is how I use it:

[<LitElement("ol-map")>]
let OlMap ()  =
    Hook.useHmr hmr
    let this, props =
        LitElement.init (fun cfg ->
            cfg.useShadowDom <- true
            cfg.props <-
                {|
                    map = Prop.Of(Map.map [], attribute = "map")
                |}
            cfg.styles <- [
                css $"{olCss}"
                // unsafeCSS olCss
                css $"""
                  .map {{
                    width: 100%%;
                    height: 80vh;
                    background: #a2e7ff;
                  }}"""
            ])
    Hook.useEffect (fun () ->
        if isNull this.shadowRoot |> not then
            let target = getShadowElementById this "map"
            props.map.Value.setTarget target
    )
    html $"""<div id="map" class="map"></div>"""

When you say final build mode, you mean the output of fable --run vite build?

from fable.lit.

Lit has a restriction that styles must be statically declared with the css tagged template (so they can be analyzed and ensure they don't contain malicious code): https://lit.dev/docs/components/styles/#expressions

The error is misleading, it seems we're missing a Promise.catch here to show the actual error:

from fable.lit.

What is then the correct way of getting a css package into a (shadowed) component? I'm interfacing OpenLayers to Fable (I'll release the package in due time), and OpenLayers comes with a bunch of css, and it would be nice (but not strictly necessary) to contain it in the Lit component.

from fable.lit.

One thing that the shadow DOM has is that it was not designed to work with global styles so this tends to create a lot of friction when you try to integrate with third party style libraries.

The simplest and fastest workaround would be to just not use shadow DOM if you depend heavily on third party css or while not optimal but doable you can add a style/link tag inside your shadow DOM component and it should work properly

but for completeness the ideal thing though would be to use css import assertions
please note that while css assertions are already on the spec it is only supported in chrome and thus needs a polyfill

// please note that Fable doesn't have an out of the box
// way to import css/json assertions so you need to create 
// cssImport manually somehow
let styles: obj = cssImport "dependency.css"
// inside the config function
cfg.styles <- [ css $".my-local-style {{ display: flex }}"; unbox styles]

That being said I made a project which hasn't been updated in a while that covers this use case it's called Fable.ShadowStyles and you can see me hacking my way around thanks to vite here and using them here

from fable.lit.

Thank you for your suggestions @AngelMunoz!

from fable.lit.