Uosis

> Other potential concerns would be – what if the user starts to interact with the website before we load the interactive Laminar app, like, what if they focus on...

As a workaround, something like this can be added to the `./mill` wrapper script: ```shell if [ "$1" = "bloop" ] ; then exec $MILL_EXEC_PATH mill.contrib.Bloop/install elif [ "$1" =...

Unfortunately no plans to update at this time.

Yeah web components are asynchronous by design - there is `WebComponentsReady` event, similar to `DOMReady`, that you need to wait for before you can call methods on web components. See...

Yep `lorri gc` would work just as well. Though I don't really see any harm in putting files in "project" directories - in our usage of lorri, if a directory...

@mathieuleclaire if you are still playing around with this, I pushed a fix [here](https://github.com/uosis/laminar-web-components/compare/fix-mwc-list-item). The problem was that for this particular component, NPM package name does not match the required...

This looks like the js import is still missing - did you rebuild components package from that branch? ```shell cd material sbt publishLocal cd ../examples/showcase sbt fastOptJS::webpack ```

> My generator doesn't even have support for different npm package vs import, so at this point if you run the generator, you need to edit the output manually to...

No, it's not as simple - we need to add support to the generator and component definitions to specify `@JSImport` name independently from NPM package name. Currently it assumes that...

> Fixed on tablesaw-parquet side with [v0.11.0](https://github.com/tlabs-data/tablesaw-parquet/releases/tag/0.43.1-v0.11.0). While this is great and probably the most expedient solution (thanks @ccleva for a quick fix!), the underlying problem of broken init is...