develwoutacause’s Twitter Archive

29 results for extension

1. develwoutacause’s Twitter Archive—№ 1,772

   of design docs from the Chrome team about supporting enterprise extensions and no content at all about how to make a Google-internal extension.🤦‍♂️.

2. develwoutacause’s Twitter Archive—№ 116

   The project was called #BXPB - "Browser eXtension Protocol Buffers" (I know, I'm bad names). https://github.com/dgp1130/bxpb. github.com/dgp1130/bxpb This was a library intended to solve a common problem I've encountered a

3. develwoutacause’s Twitter Archive—№ 133

   These features simply aren't very useful for browser extensions' internal use: 1. Extensions are released monolithically, so version skew and wire compatibility aren't an issue. 2. Communication stays on the

4. develwoutacause’s Twitter Archive—№ 5

   TIL that you can write custom "require extensions" in Node, which makes it run custom code when you require files matching a certain extension. You could dynamically compile TypeScript, protocol

5. develwoutacause’s Twitter Archive—№ 47

   It's so sad to see Chrome extension infrastructure diverging from web like this for no apparent reason. @ChromeDevTools is there a reason behind this discrepancy? DevTools itself supports dark theme,