Add quick start commands, test auth patterns (JWT not APIKEY), plugin installation internals, monorepo structure, plugin repository layout, and workspace information. Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
6.4 KiB
Agent Guide - Etherpad
Welcome to the Etherpad project. This guide provides essential context and instructions for AI agents and developers to effectively contribute to the codebase.
Project Overview
Etherpad is a real-time collaborative editor designed to be lightweight, scalable, and highly extensible via plugins.
Technical Stack
- Runtime: Node.js >= 20.0.0
- Package Manager: pnpm (>= 8.3.0)
- Languages: TypeScript (primary for new code), JavaScript (legacy), CSS, HTML
- Backend: Express.js 5, Socket.io 4
- Frontend: Legacy core (
src/static), Modern React UI (ui/), Admin UI (admin/) - Database: ueberdb2 abstraction (supports dirtyDB, MySQL, PostgreSQL, Redis)
- Build Tools: Vite (for
uiandadmin), esbuild, tsx - Testing: Mocha (backend), Playwright (frontend E2E), Vitest (unit)
- Auth: JWT (jose library), OIDC provider
Directory Structure
src/node/- Backend logic, API handlers, database models, hookssrc/static/- Core frontend logic (legacy jQuery-based editor)src/static/js/pluginfw/- Plugin framework (installer, hook system)src/tests/- Test suites (backend, frontend, container)ui/- Modern React OIDC login UI (Vite + TypeScript)admin/- Modern React admin panel (Vite + TypeScript + Radix UI)bin/- CLI utilities, build scripts, plugin management toolsbin/plugins/- Plugin maintenance scripts (checkPlugin.ts, updateCorePlugins.sh)doc/- Documentation (VitePress + Markdown/AsciiDoc)local_plugins/- Directory for developing and testing plugins locallyvar/- Runtime data (logs, dirtyDB, etc. - ignored by git)
Quick Start
pnpm install # Install all dependencies
pnpm run build:etherpad # Build admin UI and static assets
pnpm --filter ep_etherpad-lite run dev # Start dev server (port 9001)
pnpm --filter ep_etherpad-lite run prod # Start production server
Core Mandates & Conventions
Coding Style
- Indentation: 2 spaces for all files (JS/TS/CSS/HTML). No tabs.
- TypeScript: All new code should be TypeScript. Strict mode is enabled.
- Comments: Provide clear comments for complex logic only.
- Backward Compatibility: Always ensure compatibility with older versions of the database and configuration files.
Development Workflow
- Branching: Work in feature branches. Issue PRs against the
developbranch. Never PR directly tomaster. - Commits: Maintain a linear history (no merge commits). Use meaningful messages in the format:
submodule: description. - Feature Flags: New features should be placed behind feature flags and disabled by default.
- Deprecation: Never remove features abruptly; deprecate them first with a
WARNlog. - Forks: For etherpad-lite changes, commit to
johnmclear/etherpad-litefork on a new branch, then PR toether/etherpad-lite. For plugins (ep_*repos), committing directly is acceptable.
Testing & Validation
- Requirement: Every bug fix MUST include a regression test in the same commit.
- Backend Tests:
pnpm --filter ep_etherpad-lite run test - Frontend E2E Tests:
pnpm --filter ep_etherpad-lite run test-ui - Admin Tests:
pnpm --filter ep_etherpad-lite run test-admin - Linting:
pnpm run lint - Type Check:
pnpm --filter ep_etherpad-lite run ts-check - Build:
pnpm run build:etherpadbefore production deployment
Backend Test Auth
Tests use JWT authentication, not API keys. Pattern:
import * as common from 'ep_etherpad-lite/tests/backend/common';
const agent = await common.init(); // Starts server, returns supertest agent
const token = await common.generateJWTToken();
agent.get('/api/1/endpoint').set('authorization', token);
Do not use APIKEY.txt — it may not exist in the test environment.
Key Concepts
Easysync
The real-time synchronization engine. It is complex; refer to doc/public/easysync/ before modifying core synchronization logic.
Plugin Framework
Most functionality should be implemented as plugins (ep_*). Avoid modifying the core unless absolutely necessary.
Plugin structure:
ep_myplugin/
├── ep.json # Hook declarations (server_hooks, client_hooks)
├── index.js # Server-side hook implementations
├── package.json
├── static/
│ ├── js/ # Client-side code
│ ├── css/
│ └── tests/
│ ├── backend/specs/ # Backend tests (Mocha)
│ └── frontend-new/ # Frontend tests (Playwright)
├── templates/ # EJS templates
└── locales/ # i18n files
Plugin management:
pnpm run plugins i ep_plugin_name # Install from npm
pnpm run plugins i --path ../plugin # Install from local path
pnpm run plugins rm ep_plugin_name # Remove
pnpm run plugins ls # List installed
Plugin installation internals: Plugins are installed to src/plugin_packages/ via live-plugin-manager, which stores them at src/plugin_packages/.versions/ep_name@version/. Symlinks are created: src/node_modules/ep_name → src/plugin_packages/ep_name → .versions/ep_name@ver/.
Plugin Repositories
- Monorepo:
ether/ether-pluginscontains 80+ plugins with shared CI/publishing - Standalone repos: Individual
ether/ep_*repos still exist for many plugins - Plugin CI templates:
bin/plugins/lib/contains workflow templates pushed to standalone plugin repos viacheckPlugin.ts - Shared pipelines:
ether/ether-pipelinescontains reusable GitHub Actions workflows for plugin CI
Settings
Configured via settings.json. A template is available at settings.json.template. Environment variables can override any setting using "${ENV_VAR}" or "${ENV_VAR:default_value}".
Monorepo Structure
This project uses pnpm workspaces. The workspaces are:
src/- Core Etherpad (package:ep_etherpad-lite)bin/- CLI tools and plugin scriptsui/- Login UIadmin/- Admin paneldoc/- Documentation
Root-level commands operate across all workspaces. Use pnpm --filter <package> to target specific workspaces.
AI-Specific Guidance
AI/Agent contributions are explicitly welcomed by the maintainers, provided they strictly adhere to the guidelines in CONTRIBUTING.md and this guide. Always prioritize stability, readability, and compatibility.