Getting started with React & GraphQL part I
React is the most popular among front end frameworks.
GraphQL is the top most wanted technology to learn.
Following that, I've combined popular boilerplates and starter apps to start using React with GraphQL. There's so much stuff on the internet that I've decided to split article two articles.
- SaaS Boilerplate
- React apollo todo app
- Universal React Apollo app
- Relay Skeleton
###Universal React+GraphQL starter kit: React 16, Apollo 2, MobX, Emotion, Webpack 4, GraphQL Code Generator, React Router 4, PostCSS, SSR.
- React v16.8 (the one with hooks!) for UI.
- Apollo Client 2.5 (React) for connecting to GraphQL.
- MobX-React-Lite for declarative, type-safe flux/store state management.
- Emotion CSS-in-JS, with inline
<style>tag generation that contains only the CSS that needs to be rendered.
- Sass, Less and PostCSS when importing
- React Router 4 for declarative browser + server routes.
- GraphQL Code Generator v1.1 for parsing remote GraphQL server schemas, for automatically building fully-typed Apollo React HOCs instead of writing
<head>section, using react-helmet.
- Built-in Koa 2 web server, with async/await routing.
- Full route-aware server-side rendering (SSR) of initial HTML.
- Universal building - both browser + Node.js web server compile down to static files, for fast server re-spawning.
- Per-request GraphQL store. Store state is dehydrated via SSR, and rehydrated automatically on the client.
- MobX for app-wide flux/store state, for automatically re-rendering any React component that 'listens' to state. Fully typed state!
- Full page React via built-in SSR component - every byte of your HTML is React.
- SSR in both development and production, even with hot-code reload.
- Hot code reloading; zero refresh, real-time updates in development.
- Development web server that automatically sends patches on code changes, and restarts the built-in Web server for SSR renders that reflect what you'd see in production.
subscriptionquery support for real-time data (just set
- Webpack v4, with tree shaking -- dead code paths are automatically eliminated.
- Asynchronous code loading when
import()'ing inside a function.
- Automatic per-vendor chunk splitting/hashing, for aggressive caching (especially good behind a HTTP/2 proxy!)
- Gzip/Brotli minification of static assets.
- CSS code is combined, minified and optimised automatically - even if you use SASS, LESS and CSS together!
- Emotion, for writing CSS styles inline and generating the minimal CSS required to properly render your components.
- PostCSS v7 with next-gen CSS and automatic vendor prefixing when importing
- SASS and LESS support (also parsed through PostCSS.)
- Automatic vendor prefixing - write modern CSS, and let the compiler take care of browser compatibility.
- Mix and match SASS, LESS and regular CSS - without conflicts!
- CSS modules - your classes are hashed automatically, to avoid namespace conflicts.
- Compatible with Foundation, Bootstrap, Material UI and more. Simply configure via a
.global.(css|scss|less)import to preserve class names.
- Production bundling via
npm run production, that generates optimised server and client code.
- Static compression using the Gzip and Brotli algorithms for the serving of static assets as pre-compressed
.brfiles (your entire app's
main.js.bz- including all dependencies - goes from 346kb -> 89kb!)
- Static bundling via
npm run build:static. Don't need server-side rendering? No problem. Easily deploy a client-only SPA to any static web host (Netlify, etc.)
###SaaS Boilerplate + examples using React, Relay, GraphQL, Node.js, and Cassandra/Elassandra.
|found||Extensible route-based routing for React applications.|
|GraphQL||A query language for describing the capabilities and requirements of data models for client‐server applications.|
|Material UI||Library for implementing Material Design in React. All user interface in this kit is built predominantly using Material UI components.|
|React||The best library for building modern browser-based and mobile UIs.|
|React Helmet||Reusable React component will manage all of your changes to the document head with support for document title, meta, link, script, and base tags.|
|Apache Cassandra||The right choice when you need scalability and high availability without compromising performance. Linear scalability and proven fault-tolerance on commodity hardware or cloud infrastructure make it the perfect platform for mission-critical data. Cassandra's support for replicating across multiple datacenters is best-in-class, providing lower latency for your users and the peace of mind of knowing that you can survive regional outages.|
|Data Loader||Generic utility to be used as part of your application's data fetching layer to provide a consistent API over various backends and reduce requests to those backends via batching and caching.|
|Elassandra||Elassandra Combines Cassandra And Elasticsearch In A Single Powerful Integrated Solution. URB works well with Elassandra.|
|Express||Fast, unopinionated, minimalist web framework for Node.js|
|express-cassandra||Cassandra ORM/ODM/OGM for Node.js with optional support for Elassandra & JanusGraph|
|Express GraphQL||A Node.js express library that allows the creation of GraphQL servers.|
|JWT||JSON Web Tokens is an industry standard RFC 7519 method for representing claims securely between two parties.|
|Winston||A logger for just about everything.|
|Babel||Transpiles ESX to ESX and performs relay transformations.|
|concurrently||Run multiple commands concurrently.|
|Husky||Git hooks for eslint and prettier.|
|LocalTunnel||Expose yourself to the world.|
|React Hot Loader||Allows tweaking of React components in real time.|
|Webpack||Bundles npm packages, application Java Script, CSS, images, etc. into bundles.|
###A simple todo app build on react using the graphql queries of hasura
This is a basic todo app built on react. The app uses Hasura for its backend, leveraging the following features of Hasura:
- Deploy the react app
- Hasura Authentication the Auth UI Kit
- Hasura Database
- GraphQL queries provided by Hasura
This project comes with the following custom microservice - a React TODO app made using GraphQL with Apollo Client
###Universal React Apollo App (GraphQL) consuming
- GraphQL for fetching data! The most awesome part of the project!
- Universal Rendering (Server Side Rendering)
- ES6/ES2015 with Babel
- React data container for the Apollo Client
- Integrating predictable state container Redux with Apollo
- Hot reloading using React-Hot-Loader
- Recompose as a React utility belt for higher order components
- Development and production bundling by Webpack
- CSSNext: use of official W3C syntax of the future CSS
- Transforming styles with JS plugins by PostCSS
- Wow.js for CSS animations
- Flexbox for resolving layout fatigue and making the app responsive (open the app in desktop, mobile, whatever...). Doesn't work on IE 9, but it should not be a problem nowadays. See browsers usage.
- CSS Modules: say goodbye to global scope in CSS and most of conflicts
- Jest Snapshot Testng, some parts in Enzyme and Sinon
- Linting both JS and CSS, respectively by: ESLint and Stylelint
###React, Relay, GraphQL project skeleton
This skeleton project is meant to scaffold a fullstack React, Relay, and GraphQL project. The skeleton uses webpack and gulp to manage the build and provide a great development experience. The frontend stack is React, and Relay. All React changes are automatically hot reloaded using react-hot-loader. Also, the backend server is automatically restarted upon any changes using nodemon.
Both the server and frontend code are built and transpiled using webpack, while gulp is used primarily to start the webpack-dev-server and nodemon.
This skeleton was designed with a typical use case of having a backend api serve a React SPA. The skeleton automatically proxies all requests to
/graphql thru the webpack-dev-server to the backend GraphQL server.
The frontend is automatically hot reloaded whenever you save a file. See [react-hot-loader] for more details on how this works. It enables you to immediately see changes in React components without losing application state or having to reload your page!
The backend server is automatically restarted whenever you save a file.
If, for example, you modify the GraphQL schema, then the GraphQL server will be restarted to reflect the changes, the
schema.json will be regenerated using an introspection query, and the frontend code will be recompiled to re-run
Relay.QL queries through the