How brumm/tako works
Project type and purpose
• This is a browser extension (Chrome and Firefox) named “Tako” whose purpose is to inject an inline, expandable GitHub file tree with file preview directly into GitHub repository pages.
• It uses React components to render the UI, content scripts to inject that UI into GitHub pages, and a background script to handle persistent state (e.g., tokens) and messaging.
File structure
• Top-level files:
• package.json, webpack.config.js – build and dependency configuration
• media/ – extension logo, screenshots
• README.md, TODO.txt, LICENSE
• src/:
• entry-background.js → background entry point
• entry-content-script.js → content-script entry point
• background.js → background logic (token storage, messaging listeners)
• api.js, github-relative-time.js, queryClient.js, storage.js, utils.js – utility layers for networking, caching, storage
• import-extension-assets.js, template.html.ejs – build-time asset injection
• components/ – pure React UI components (App, Listing, Preview, Error boundaries, etc.)
• constants.js, hooks.js
• webpack.config.js builds two output bundles (background & content script) plus EJS-templated HTML for packaging.
README for additional insights
• Confirms it is injected into GitHub repos in dev and production mode
• Build commands produce zipped extension packages for Chrome/Firefox