Skip to content


Switch branches/tags

Latest commit


Git stats


Failed to load latest commit information.
Latest commit message
Commit time


Monikerz is a party game that is similar to Celebrity or Charades. Teams play against each other by trying to guess as many names as possible before time runs out.

Tech Stack

  • React: UI components
  • Redux: Firestore state management
  • XState: Game state machine
  • Firebase: Backend / real-time updates
  • Fontawesome: Icons
  • Fathom: Analytics
  • Honeybadger: Error Reporting


It is recommended to use VS Code for development. There are recommended extensions for this repository. It is also recommended that you install the chrome extensions associated with debugging the react, redux, and xstate libraries.

Environment Variables

Note that changing an environment variable requires restarting webpack.

Variable Description
DEBUG_BUNDLE_SIZE Enabled webpack-bundle-analyzer to check on bundle bloat
DEBUG_FIREBASE Enables firebase logging to the console, when in development mode
DEBUG_REDUX Enables redux-logger to output to the console, when in development mode
DEBUG_RENDER Enables why-did-you-render to help troubleshoot unnecessary component updates, when in development mode
FATHOM_SITE_ID Site ID for Fathom Analytics, when in production mode
FIREBASE_* Firebase config values for interacting with firestore and dynamic links APIs. These come from the firebase web console.
HONEYBADGER_API_KEY Honeybadger API key for error reporting and sourcemap upload, when in production mode
HONEYBADGER_ASSETS_URL Base URL for production assets, required for honeybadger-webpack in production mode


  1. Ensure node and yarn are installed globally.
  2. Clone this repository.
  3. Copy .env.example to .env and configure the relevant environment variables. See above for descriptions.
  4. Run yarn install from the root of the repository.
  5. Run yarn dev:dll once to build the webpack dll of dependencies.
  6. Run yarn dev to start webpack in watch mode. This will automatically open your default browser.
  7. Run yarn test to check that your tests pass ok.
  8. Run yarn test:coverage to check that coverage has not decreased.
  9. If you've built a shared component, create a story for it in Storybook.
  10. When your changes are complete, ensure your branch is up to date, has no conflicts, and is squashed down to one commit.Then, push your change to a branch against this repository or your fork.
  11. Create a pull request and ensure it passes CI (which should be equivalent to running yarn test). Only pull requests that pass the aforementioned checks will be accepted.


This workflow builds on the above, so ensure you're able to build locally in dev mode before trying to create a production release.

  1. Ensure you're on master and have the latest commits checked out.
  2. Ensure .env is up to date.
  3. Ensure firebase-tools are installed globally.
  4. Bump the version number in package.json.
  5. Run yarn prod:dll once to build the webpack dll of dependencies.
  6. Run yarn prod to create a release build. Note that running this command will upload sourcemaps to honeybadger.
  7. Run yarn deploy to push the release up to firebase.
  8. Commit to master with the updated version number and firebase cache file.


A party game that is similar to Celebrity or Charades







No releases published


No packages published