Cwant to know what sort of benefits this has over the current 'just console log it'
Chmm i don't know if its the same but I did the chrome extension demo 
... just that hahah
... just that hahahCList all World Documents, kind of souped up version of "print to console" could be useful
CA flag editor/document editor which manually
updateI mentioned hooks as a half joke but it would be nice. very level-0 shit, a toggle to log hooks or not
Cyeah but devmode already does that
Cyeah but it could replace it 
Cagreed, it would have a place in this
Clocalization shit ? I don't know how accessible it might be
Cdebug tools has access to like the profiler and shit I think
Cwonder how a 'custom foundry profiler' might look
Ci know react devtools has stuff like that
Cbut been able to see maybe the tree of translations could be handy, for like when you are translating a module/system onto another module, so you could double check where each localized text is coming from
Coh yeah this uses a manifest too, it looks rather similar too, seems to be using service workers on a similar fashion but registering different parts of the API
CChrome Developers
Step-by-step instructions on how to create a Chrome Extension.
ADF Flag Editor already exists btw
Csure, but I mean, it's totally a module/system dev tool, we could work on integrating it into this devmode or do something similar
Cwhile im all in for smaller.. more.. emm.. modular? modules in general usage terms, as one game might not require what other does, or one system from another, or even users might prefer other module for doing this or that thingy, the fvtt development space does feel like the right spot to amalgamate these modules into more comprehensive tools.
Cmore interested from the perspective of "a chrome extension might work even if the foundry UI fails to initialize"
Cdidn't even consider that point, also love it
AHow often will the UI fail to that degree, but still load module scripts?
AIt's never happened to me that the UI is broken and scripts still load
CI think the goal is that this will not be a module, so it would not go through the same flow
C^
Cas a chrome extension it wouldn't be a module at all yeah
AAh 
C@arcanist this would be implemented using something similar to the PWA thingy you did, uses a similar manifest and shit
AOh, yeah. You realize that means that users must manually copy the service worker into their folder since modules can't download JavaScript there
AI originally tried putting the service worker in the module folder, but that doesn't work because it's scoped to sub-directories
Chmm
ADoes it require a service worker?
Cas far as I understand (with like a five minute investment of time two days ago) yes
CChrome Developers
Build the next generation of web experiences.