How jinbekim/gitlab-pn works
Project Type: Browser Extension (Chrome Extension)
This is a browser extension project specifically designed for GitLab, likely for customizing notification or text display functionality.
Browser Context Components
a) Content Script Context (inject/)
b) Popup Context (popup/)
Extension Architecture
• Create three main sections:
a) User Interface Layer (Popup)
• Popup/index.html
• Popup/index.css for styling
• Popup/index.ts for popup logic
b) Content Script Layer (Inject)
• Inject/index.ts which interacts with the webpage
c) Shared Utilities
• Utils/index.ts as a shared module
Communication Flow
• Popup <-> Chrome Extension API
• Content Script <-> Webpage DOM
• Popup <-> Content Script (via Chrome messaging)
Technical details
• TypeScript compilation flow (*.ts -> dist/*.js)
• manifest.json as the configuration hub
• Chrome Extension API integration points
Layout Guidelines:
Top Section
• Relationship with Chrome Extension API
Middle Section
• Content script interaction with webpage
• Message passing between components
Bottom Section
• Shared utilities and build artifacts
Additional Considerations:
Build Process
• TypeScript compilation flow
• How dist/ folder is generated
Configuration
• Manifest.json role
• Permissions and content script injection points
Asset Management
• Img/ directory for extension resources
Remember to:
• Use consistent styling for similar components
• Version information if relevant
• Clear boundaries between extension contexts