Skip to content

Commit

Permalink
Fix production build (#265)
Browse files Browse the repository at this point in the history
* Fix production build

The production build failing was the result of a bug related to an older version react-scripts not playing nice with the latest version of graphql (graphql/graphql-js#1248).

Updating to the latest version of react-scripts (v2.1.1) fixed the bug. It also reduces the production build *considerably* (from over 1mb down to 48kb).

* Downgrade babel-preset-react-app to 3.1.0
  • Loading branch information
adamsoffer authored and Randy1Burrell committed Dec 7, 2018
1 parent 4fcb29a commit ada1d13
Show file tree
Hide file tree
Showing 2 changed files with 512 additions and 88 deletions.
4 changes: 2 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,7 @@ The quickest way to run a Graph Node locally is to use the
This will automatically provision a server with rust, postgres, and ipfs, and
spin up a graph node with a GraphiQL interface at `http://127.0.0.1:8000/`.
Congrats, you're now ready to build and deploy the Livepeer subgraph. You may
skip ahead to [Building & deploying the Subgraph](#building-&-deploying-the-livepeer-subgraph)
skip ahead to [Building & deploying the Subgraph](#building-and-deploying-the-livepeer-subgraph)

### Running a local Graph Node _without_ Docker

Expand Down Expand Up @@ -64,7 +64,7 @@ optional, it depends on your setup.

This will also spin up a GraphiQL interface at `http://127.0.0.1:8000/`.

### Building & deploying the Livepeer Subgraph
### Building and Deploying the Livepeer Subgraph

Back in our subgraph directory, run

Expand Down
Loading

0 comments on commit ada1d13

Please sign in to comment.