If you see a step below that could be improved (or is outdated), please update the instructions. We rarely go through this process ourselves, so your fresh pair of eyes and your recent experience with it, makes you the best candidate to improve them for other users. Thank you!
- Make sure you have Node.js version >= 10.
- We recommend using nvm:
nvm use.
We recommend cloning the repository in a folder dedicated to opencollective projects.
git clone git@github.com:opencollective/opencollective-frontend.git opencollective/frontend
cd opencollective/frontend
npm install
This project requires an access to the Open Collective API. You have two options:
cp .env-staging .envto connect to the Open Collective staging APIcp .env-local .envto connect to the API running locally
If you decide to pick the local strategy, make sure you install and run the opencollective-api project.
npm run dev
Code style? Commit convention? Please check our Contributing guidelines.
TL;DR: we use Prettier and ESLint, we do like great commit messages and clean Git history.
You can run the tests using npm test or more specifically:
npm run test:srcfor pages and componentsnpm run test:serverfor apinpm run test:e2efor end-to-end tests using Cypress
To update the Jest snapshots, run npm run test:update
To add a translation to a new language, copy paste the en.json from src/lang and rename the copy using the 2 or 4 letter code for your country/language (e.g. fr-BE.json or fr.json).
You will also need to copy paste the last line in scripts/translate.js, and replace ja with your 2-4 letter locale code.
fs.writeFileSync(`${LANG_DIR}ja.json`, JSON.stringify(translatedMessages('ja'), null, 2));
To deploy to staging or production, you need to be a core member of the Open Collective team.
npm run deploy:staging
URL: https://staging.opencollective.com/
npm run deploy:production