raquo/laminar-full-stack-demo

Fully working client + server, dev + prod setup for Scala.js development, showcasing a bunch of Laminar & Scala.js patterns.

laminar-full-stack-demo's Issues

News & Updates Thread

I'll be posting laminar-demo updates here, e.g. when I add more examples, or start doing things differently.

Click the subscribe button on this issue in Github to get notified.

For questions / discussion, please go to Laminar discord, or the #scala-js channel on the Scala discord, if it's not specifically about Laminar.

A couple updates, to start with:

• I've improved and published the Vite plugins that used to live in this repo to npm:
  • https://github.com/raquo/vite-plugin-import-side-effect
    • v0.2 of this plugin has a new interface and a much better implementation
    • v0.2 replaces JSImportSideEffect with more standard importing syntax (with optional compact syntax)
  • https://github.com/raquo/vite-plugin-glob-resolver
• This repo contains manually written bindings for a couple Shoelace.js web components. To scale this up, I've started working on a generator of Web component bindings for Laminar (and other Scala.js libraries): https://github.com/raquo/laminar-shoelace-components

JsRouter incremental compilation problem

You might have noticed that sometimes when adding a new page, you get an incremental compilation error like "ThatNewPage does not exist" which does not go away until you sbt clean. This seems to be this bug In Scala 3. I made a small reproduction for it, so hopefully the fix is coming.

As a workaround, after you create a new Page, you need to save the pages.scala file BEFORE you use the page anywhere. Or, you can change JsRouter by removing the export of pages, and using Scala 2 patterns for that.

Upstream weather service partial outage is not handled

Thanks for the fantastic repo, this has been a very useful learning tool.

I had it working at first, but at some point the upstream API call at WeatherFetcher.scala line 26 is returning an empty currentConditions element. This would have been more confusing if it happened when I was first trying to get it going. When this problem first started, both Squamish and Netinat were failing. At the current moment, Netinat is working, but Squamish is still out.

I found this comment on a similar issue for a different region here (home-assistant/core#101533 (comment)) so maybe this is something that the code should be able to more gracefully handle. Although I could see if you want to leave it as is to keep the example pure. Maybe even just make a few more stations available, and add a warning that they could be out would help?