An alternative web client for Mastodon, focused on speed and simplicity.

Go to file

Nolan Lawson 59e895f814 fix tests		2018-03-08 22:18:40 -08:00
assets	…
bin	fix tests	2018-03-08 22:18:40 -08:00
fixtures	add failing test for offline threads	2018-03-08 18:08:14 -08:00
original-assets	…
routes	fix offline threads	2018-03-08 18:31:59 -08:00
scss	add footer and license	2018-03-07 09:25:07 -08:00
templates	add failing test for offline threads	2018-03-08 18:08:14 -08:00
tests	fix tests	2018-03-08 18:37:32 -08:00
.gitignore	…
LICENSE	add footer and license	2018-03-07 09:25:07 -08:00
README.md	…
package-lock.json	fix media uploads in restoration script	2018-03-05 23:46:50 -08:00
package.json	fix test setup process	2018-03-06 09:21:17 -08:00
server.js	…
webpack.client.config.js	fix sourcemap config	2018-03-04 16:42:04 -08:00
webpack.server.config.js	…

README.md

Pinafore

An alternative web client for Mastodon.

Building

npm install
npm run build
PORT=4002 npm start

Development

npm run dev

Testing in development mode

In separate terminals:

1. Run a Mastodon dev server (note this destroys the mastodon_development database and inserts canned data):

npm run run-mastodon

2. Run a Pinafore dev server:

npm run dev

3. Run a debuggable TestCafé instance:

npx testcafe --hostname localhost --skip-js-errors --debug-mode firefox tests/spec

If you want to export the current data in the Mastodon instance as canned data, so that it can be loaded later:

npm run backup-mastodon-data

Testing

Lint:

npm run lint

Run integration tests:

npm test

Run tests for a particular browser:

BROWSER=chrome npm run test-browser
BROWSER=chrome:headless npm run test-browser
BROWSER=firefox npm run test-browser
BROWSER=firefox:headless npm run test-browser
BROWSER=safari npm run test-browser
BROWSER=edge npm run test-browser

Automatically fix most linting issues:

npx standard --fix