How emrecpp/cookify works
Project Type and Purpose
• Cookify is a Chrome Extension (not a web server or microservice).
• Purpose: Provide a popup UI for managing cookies, JWT tokens, and integrate those directly into Swagger API docs.
File Structure
• manifest.json: Entry point; defines extension capabilities (popup, content scripts, permissions).
• Root index.html + src/: The popup UI built with React & TypeScript, assembled by Vite.
• src/main.tsx → src/app/App.tsx → pages/components (cookie, swagger, settings)
• content-script/: A second React app that gets injected into matching web pages (Swagger UI).
• content-script/src/main.tsx → content-script/src/App.tsx
• src/context, src/hooks, src/lib, runtime/helpers: Internal logic, state management, utilities, schema validation (Zod).
• build/config: Vite, ESLint, Tailwind, TypeScript configs.
Main Components
A. Browser (Chrome) Host
• The runtime environment that loads the extension.
B. Extension Manifest
• Defines two entry points:
1. Popup UI (loaded in extension toolbar popup)
2. Content Script (injected into Swagger pages)
C. Popup React App
• Built from src/app; provides:
• Cookie management UI
• JWT token management UI
• Project grouping, import/export
• Interacts with Chrome APIs directly (chrome.cookies, chrome.storage, chrome.tabs, chrome.runtime).
D. Content-Script React App
• Injected into Swagger pages.
• Listens for messages (chrome.runtime.onMessage) to:
• Apply cookies to document via document.cookie or chrome.cookies
• Insert JWT into Swagger’s Authorization header input
E. Chrome Extension APIs
• chrome.cookies: read/write cookies on target domains
• chrome.storage: persist saved cookies/tokens and profiles
• chrome.runtime.messaging: communication between popup and content script
F. External Swagger UI
• The web page where content-script injects UI elements and updates auth fields
Relationships & Data Flow
1. User Interaction in Popup → triggers React state updates → calls Chrome APIs (cookies/storage)
2. Popup sends message to active tab’s Content Script:
• e.g. “Apply this cookie set” or “Set this JWT token”
3. Content Script acts on the DOM/Swagger UI or uses chrome.cookies API
4. Data Persistence flows to/from chrome.storage (for import/export profiles)
Architectural Patterns & Technologies
• Component-Based UI with React (Popup & Content Script)
• Context + Custom Hooks for global state and side-effects (useCookie, useSwagger)
• Message-Passing pattern between popup and content script
• Schema Validation via Zod (src/lib/schemas.ts)
• Vite build tooling for bundling two entry points