Contribute & develop

Set up a local checkout#

Configure .env, start the backend with npm run start, and load the extension folder as unpacked in Chromium or temporarily in Firefox. Set Custom Server to your local origin and complete Scratch Auth. Use separate accounts to verify collaboration.

git clone https://github.com/Waakul/CoBlocks.git
cd CoBlocks/backend
npm ci
cp .env.example .env

Run the repository checks#

The lint command covers backend and extension source. Existing tests cover authentication, project access, invites, browser compatibility, backpack, pointers, presence, sessions, and snapshot/storage recovery. Run checks relevant to your changes and record their results.

The bundled extension/background/socket.io.js is third-party generated code. Rebuild or update its dependency through repository tooling; do not patch the bundle by hand.

# From backend/
npm run lint
npm test

Prepare a useful contribution#

• Search existing issues and describe the user problem before a large change.
• Keep the change focused; preserve unrelated local edits.
• Include reproduction/verification steps, browser and extension versions, and screenshots for visual changes.
• Do not include .env, authentication tokens, private invite URLs, generated storage, or user chat data.
• For an access-control or authentication weakness, contact the maintainer before publishing exploit details in a public issue.

Keep the wiki accurate#

Check a released tag and its notes before describing something as shipped. New local source is not automatically a distributed feature. Every guide includes source references and the verified release date.

Use real screenshots of the described version when available. The supplied popup screenshots in this wiki show an earlier v0.3.0-pre header; captions identify that difference. Do not use a mockup to imply a control exists.