How pnd280/complexity works
Project Type and Purpose
• This is a monorepo (pnpm + Turbo) containing:
– Reusable packages (async-dep-manager, cli-logger, eslint-config, i18n, typescript-config, webext-bridge)
– A browser-extension (“perplexity/extension”) built in TypeScript + React + Vite targeting Perplexity AI (Chrome/Firefox)
• Purpose: deliver a highly modular, customizable suite of UI/UX enhancements—via a plugin system—for AI chat web apps
File-Structure Analysis
• Top level: monorepo config (.gitignore, pnpm-workspace.yaml, turbo.json, Husky, VSCode, ESLint, TypeScript)
• packages/: small libraries providing core capabilities (async-registry, CLI logger, i18n support, shared configs)
• perplexity/extension/: the extension’s source—entrypoints (background, content-scripts, options page), React components, services, plugin modules, tests, CLI, docs, build (Vite, gulp)
Key README Insights
• “Complexity” is now a suite, originally a Perplexity AI extension—focus on modular enhancements
• Invites you to “./perplexity/extension/” for architecture details
a. Monorepo Packages Layer
– Shared packages: async-dep-manager, cli-logger, eslint-config, i18n, typescript-config
– pnpm + Turbo orchestrates build & dependency graph
b. Extension Runtime Layer
1. Manifest (chrome/firefox)
2. Entry Points
– background.ts: central hub—handles permissions, network proxy, message routing
– content-scripts: inject into pages—DOM observers, main-world integration
– options-page (React): UI for plugin configuration & dashboard
3. Services
– extension-permissions, extension-settings, instant-css, indexed-db, pplx-api, cplx-api, i18n
4. Plugin System
– plugin registry (core async-dep, cache, hooks)
– Multiple plugin modules under src/plugins/**
5. UI Components
– core UI (Toaster, Tooltip, Buttons…)
– domain UI (dashboard pages, plugin UIs)
c. Build & Delivery Layer
– CLI under perplexity/extension/cli for versioning, publishing to Chrome/AMO
– Vite + gulp build pipelines produce manifest-ready bundles
– E2E (Playwright), unit tests (Vitest)
Architectural Patterns & Principles
• Monorepo with well-defined package boundaries for reuse
• Plugin architecture: lazy-loaded plugins, async dependency registry, isolation via content scripts vs. main-world injection
• Separation of concerns:
– “Services” layer abstracts storage, network, permissions
– “UI” layer purely React + state via TanStack Query + Zustand
– “Entry points” layer wires environment specifics