browser-extensions-playground

Playground for browser scraping extensions and scraped data tooling. The repository also tracks built package artifact size with gh-build-size.

Architecture

This workspace centers on a single local scraping server.

• packages/scraping-server: unified HTTP and WebSocket server
• packages/scraping-platform: provider manifests and shared scraping helpers
• packages/scraping-extension-devtools: dangerous developer extension for remote browser control
• packages/example-com: deterministic example.com extension used for automated end-to-end testing
• packages/scraped-data: generic read-only accessors over server API
• packages/scraping-devtools: CLI/MCP client for the server-side devtools control API

Quick Start

Install dependencies:

bun install
Copy

Start the local scraping server:

cd packages/scraping-server
bun run build
bun run start -- --store-file .tmp/scraping-server/deterministic.sqlite
Copy

Build an extension and load its dist directory as an unpacked Chrome extension:

cd packages/scraping-extension-devtools
bun run build
Copy

For package-specific setup, API details, metric semantics, and MCP usage, follow the package README links above.

Usage

Build

bun run build
Copy

Test

bun run typecheck
bun run test
bun run playwright:test
Copy

Development

This repository uses lefthook to run the same checks as CI locally before commits and pushes. This brings feedback earlier without changing what CI runs.

Install the hooks once after cloning:

bunx lefthook install
Copy

Hooks

pre-commit — runs on every git commit:

Check	Command
Lint	bun run lint
Typecheck	bun run typecheck

pre-push — runs on every git push:

Check	Command
Lint	bun run lint
Typecheck	bun run typecheck
Unit tests	bun run test

Playwright / end-to-end tests are intentionally excluded from hooks and from CI because they require a browser environment. Run them locally with bun run playwright:test before merging changes that touch extension build output or runtime behaviour.

Release Versioning

Checked-in packages/*/package.json versions are the release source of truth. Before creating a GitHub release, bump the package versions in the same pull request that prepares the release. The release workflow verifies that every workspace package shares the same committed version and, for release events, that the version matches the release tag. It does not rewrite package manifests during CI.

License

MIT