Not OP, but practically all of those lines are from a package-lock.json file (6755 lines) and a changelog (541 lines). It looks like the actual source is 179 lines long.
Canvas suffers from being originally designed for use in elementary (K-12) school, and then kind of wedged into college. On the teaching side it kind of assumes that classes will always be relatively small (running a 100+ student seminar class in Canvas is a nightmare) and that you, the teacher, don't mind performing the same actions over and over and...
But, it's one of the few LMSs designed post-Web 2.0 so things that require a refresh or reload in BB, etc., generally happen much more smoothly.
I've been happily using Time Sink (https://manytricks.com/timesink/) to do this for about a year now. It does not automatically merge into a timelapse, but this is accomplished easily with ffmpeg.
But you still can't have multiple tailnets. The strategy of "have hobbyists try out the software themselves, like it, then implement it at their work" seems incompatible with this fact.
The only way to do it is if you have secondary email address domains. Say mdeeks@company.com and mdeeks@company.team. You can create a separate tailnet for company.team but you also have to roll out additional subnet routers (if you use them) that are authed on that second tailnet. Also you wont be able to easily write rules that interact with things that are not authed onto the second tailnet.
They need a first class concept of "canary" or "beta" that applies to ACLs, DNS configs, client versions, and all sorts of other toggles in the UI. It's a hard product problem and I'm not even sure how some of it should work.
I just know I need a way to test changes before I roll it out to everyone at the company. Right now there aren't good options for that.
It's more than just a work/personal split. Even at work, having "development" and "production" tailnets so that things like testing complex ACLs, inhouse apps that use tailscale via its API, etc. are possible without having everyone on the devops team create an unmanaged/non-company email so they can create their own development tailnet, and then deploy a bunch of company IP using this rogue account.
That sounds extremely risky. Apart from the fact that it makes it much harder to restrict access for leaving employees, mixing personal and work identities sounds like a recipe for disaster. What happens if a personal account gets banned? How do you enforce security rules?
I guess companies where there's not even any identity management, securing your network via tailscale is not your primary concern.