|
|
||
|---|---|---|
| .github | ||
| .idea/dictionaries | ||
| cypress | ||
| icon | ||
| public | ||
| src | ||
| .editorconfig | ||
| .gitignore | ||
| CHANGELOG.md | ||
| CONTRIBUTING.md | ||
| craco.config.js | ||
| cypress.json | ||
| LICENSE | ||
| package.json | ||
| README.md | ||
| renovate.json | ||
| tsconfig.json | ||
| yarn.lock | ||
HedgeDoc - React Client
This is the new, improved and better looking frontend for HedgeDoc 2.0. Our goal is to recreate the current frontend in react and to improve it.
Preparation
You'll need at least Node 12. We use yarn for our dependencies.
Development mode
- Clone this repo (e.g.
git clone https://github.com/codimd/react-client.git hedgedoc-react-client) - Go inside the repo (e.g.
cd hedgedoc-react-client) - Run
yarn install - Either run
yarn start:dev(expects a server running under http://localhost:3000)yarn start(makes all api calls to the same domain the react-client runs on (normally http://localhost:3001 ))
This should run the app in the development mode and open http://localhost:3001 in your browser.
The page will reload if you make edits. You will also see any lint errors in the console.
Tests
Unit
Unit testing is done via jest.
- Run
yarn test
End2End
We use cypress for e2e tests.
- Start the frontend with
yarn start - Run
yarn cy:opento open the cypress test loader - Choose your browser and test
- Let the tests run
Bundle analysis
You can inspect the generated production-bundle files to look for optimization issues.
- Run
yarn analyze - Open the generated
build/report.htmlin your favourite browser
Production mode
- Clone this repo (e.g.
git clone https://github.com/codimd/react-client.git hedgedoc-react-client) - Go inside the repo (e.g.
cd hedgedoc-react-client) - Run
yarn install - Run
yarn build
Builds the app for production to the build folder.
It correctly bundles React in production mode and optimizes the build for the best performance.
The build is minified and the filenames include a hash value of the content.