I am not sure I want to use the API when it is not that hard to get the hands of a clock going with Javascript. I know I can do the latter, but the former poses a new learning challenge that doesn't guarantee a result.
My current SVG clock is modelled on a wall clock and it has the really small text that can normally found on a clock, for example 'Made in China' and 'Quartz'. I also have a fictional brand name, plus a bezel specified with 'pathLength="60"' and a dash array.
As a design exercise, a standard clock is interesting because you have to remember the stack order of the hands, and, despite looking at clocks many thousands of times, that detail requires a modicum of thought.
I think it is a good start to get a credible wall clock that tells the time at a glance before branching out into 'cool' clocks that put design before telling the time.
I now want to add a drop shadow that changes throughout the day, as if the clock is south facing, in the northern hemisphere, corresponding to my lat/lon.
This would be easy with three js because it could be modelled, along with the entire solar system, with the camera pointed at a 3D modelled clock, however, in SVG filters, could be a while.
Getting the hands to move is the easy bit, all considered. I really don't need another API for that, but I am not in the Svelte ecosystem.