This project was bootstrapped with Create React App and is configured with:
- Typescript
- Apollo-client
- eslint
- prettier
- Husky
- AutoGenerated types from subgraph schema
First you have to fork this repository. Then you need to create an .env.local with the same content as .env.example.
You can generate the types for the GQL Queries and Subscriptions by running npm generateGQLTypes, this command will search the schema exposed by graphql (it's defined in .env.local in key REACT_APP_GRAPH_HTTP) and then will generate a file in /src/types/generatedGQL.ts with the types needed for your queries. Note that this command should be executed each time the schema changes.
In the project directory, you can run:
Runs the app in the development mode.
Open http://localhost:3000 to view it in the browser.
The page will reload if you make edits.
You will also see any lint errors in the console.
Generate GQL types related with queries and subscriptions taken for the source code. The schema used to generate the types is taken from the environment variable REACT_APP_GRAPH_HTTP.
Launches the test runner in the interactive watch mode.
See the section about running tests for more information.
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 the hashes.
Your app is ready to be deployed!
See the section about deployment for more information.
Note: this is a one-way operation. Once you eject, you can’t go back!
If you aren’t satisfied with the build tool and configuration choices, you can eject at any time. This command will remove the single build dependency from your project.
Instead, it will copy all the configuration files and the transitive dependencies (Webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except eject will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.
You don’t have to ever use eject. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.