This may be better suited for a different channel, but does anyone have any clues why my re-frame application is chugging memory on some screens with hot-reload? I have a bunch of bugs to track down on these screens and I'm wondering what clues I might be able to gather from a hot reload doubling a bunch of things.
I am using re-frame-10x, which I bet uses track! Any clues on how to invoke dispose? Probably somewhere with a
^:dev/before-load
?That sort of thing can happen if reagent's track! feature is used and the tracker is not disposed of (with dispose!) before the page is reloaded. Then you have both the original tracking and the newly-reloaded tracking going on.
@thheller Shadow-css is really great. Definitely the best approach I've used for writing CSS.
Would you be interested in support for arbitrary values via aliases? Migrating tailwind classes like mt-[48px], it seems like it would be nice to just write :mt-48px instead of using the map form.