ERROR:  could not open extension control file "/usr/local/share/postgresql/extension/plv8.control": No such file or directory

          const {
            rows: [user],
          } = await rootPgPool.query(
            `select users.* from app_private.really_create_user(
              username => $1,
              email => $2,
              email_is_verified => false,
              name => $3,
              avatar_url => $4,
              password => $5
            ) users where users is not null`,
            [username, email, name, avatarUrl, password]
          );

          const {
            rows: [user],
          } = await rootPgPool.query(
            `select users.* from app_private.login($1, $2) users where users is not null`,
            [username, password]
          );

brew install postgresql
brew services start postgresql

git clone https://github.com/graphile/examples.git
cd examples
yarn
./setup.sh

$ yarn start
yarn run v1.13.0
$ concurrently --kill-others 'npm run server:koa2' 'npm run client:react'
[0] npm WARN lifecycle The node binary used for scripts is /var/folders/xn/mv_kd6_s3f572s7m_q8pt7580000gn/T/yarn--1551453787248-0.06708648276839879/node but npm is using /usr/local/bin/node itself. Use the `--scripts-prepend-node-path` option to include the path for the node binary npm was executed with.
[0] 
[0] > @ server:koa2 /Users/tyler/Desktop/examples
[0] > cd server-koa2; npm start
[0] 
[1] npm WARN lifecycle The node binary used for scripts is /var/folders/xn/mv_kd6_s3f572s7m_q8pt7580000gn/T/yarn--1551453787248-0.06708648276839879/node but npm is using /usr/local/bin/node itself. Use the `--scripts-prepend-node-path` option to include the path for the node binary npm was executed with.
[1] 
[1] > @ client:react /Users/tyler/Desktop/examples
[1] > cd client-react; npm start
[1] 
[0] npm WARN lifecycle The node binary used for scripts is /var/folders/xn/mv_kd6_s3f572s7m_q8pt7580000gn/T/yarn--1551453787248-0.06708648276839879/node but npm is using /usr/local/bin/node itself. Use the `--scripts-prepend-node-path` option to include the path for the node binary npm was executed with.
[0] 
[0] > [email protected] start /Users/tyler/Desktop/examples/server-koa2
[0] > if [ -x ../.env ]; then . ../.env; fi; NODE_ENV=development nodemon server.js
[0] 
[1] npm WARN lifecycle The node binary used for scripts is /var/folders/xn/mv_kd6_s3f572s7m_q8pt7580000gn/T/yarn--1551453787248-0.06708648276839879/node but npm is using /usr/local/bin/node itself. Use the `--scripts-prepend-node-path` option to include the path for the node binary npm was executed with.
[1] 
[1] > [email protected] start /Users/tyler/Desktop/examples/client-react
[1] > if [ -x ../.env ]; then . ../.env; fi; BROWSER=none PORT=$CLIENT_PORT react-scripts start
[1] 
[1] 
[1] There might be a problem with the project dependency tree.
[1] It is likely not a bug in Create React App, but something you need to fix locally.
[1] 
[1] The react-scripts package provided by Create React App requires a dependency:
[1] 
[1]   "babel-eslint": "9.0.0"
[1] 
[1] Don't try to install it manually: your package manager does it automatically.
[1] However, a different version of babel-eslint was detected higher up in the tree:
[1] 
[1]   /Users/tyler/Desktop/examples/node_modules/babel-eslint (version: 8.2.5) 
[1] 
[1] Manually installing incompatible versions is known to cause hard-to-debug issues.
[1] 
[1] If you would prefer to ignore this check, add SKIP_PREFLIGHT_CHECK=true to an .env file in your project.
[1] That will permanently disable this message but you might encounter other issues.
[1] 
[1] To fix the dependency tree, try following the steps below in the exact order:
[1] 
[1]   1. Delete package-lock.json (not package.json!) and/or yarn.lock in your project folder.
[1]   2. Delete node_modules in your project folder.
[1]   3. Remove "babel-eslint" from dependencies and/or devDependencies in the package.json file in your project folder.
[1]   4. Run npm install or yarn, depending on the package manager you use.
[1] 
[1] In most cases, this should be enough to fix the problem.
[1] If this has not helped, there are a few other things you can try:
[1] 
[1]   5. If you used npm, install yarn (http://yarnpkg.com/) and repeat the above steps with it instead.
[1]      This may help because npm has known issues with package hoisting which may get resolved in future versions.
[1] 
[1]   6. Check if /Users/tyler/Desktop/examples/node_modules/babel-eslint is outside your project directory.
[1]      For example, you might have accidentally installed something in your home folder.
[1] 
[1]   7. Try running npm ls babel-eslint in your project folder.
[1]      This will tell you which other package (apart from the expected react-scripts) installed babel-eslint.
[1] 
[1] If nothing else helps, add SKIP_PREFLIGHT_CHECK=true to an .env file in your project.
[1] That would permanently disable this preflight check in case you want to proceed anyway.
[1] 
[1] P.S. We know this message is long but please read the steps above :-) We hope you find them helpful!
[1] 
[1] npm ERR! code ELIFECYCLE
[1] npm ERR! errno 1
[1] npm ERR! [email protected] start: `if [ -x ../.env ]; then . ../.env; fi; BROWSER=none PORT=$CLIENT_PORT react-scripts start`
[1] npm ERR! Exit status 1
[1] npm ERR! 
[1] npm ERR! Failed at the [email protected] start script.
[1] npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
[1] 
[1] npm ERR! A complete log of this run can be found in:
[1] npm ERR!     /Users/tyler/.npm/_logs/2019-03-01T15_23_08_817Z-debug.log
[1] npm ERR! code ELIFECYCLE
[1] npm ERR! errno 1
[1] npm ERR! @ client:react: `cd client-react; npm start`
[1] npm ERR! Exit status 1
[1] npm ERR! 
[1] npm ERR! Failed at the @ client:react script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
[1] 
[1] npm ERR! A complete log of this run can be found in:
[1] npm ERR!     /Users/tyler/.npm/_logs/2019-03-01T15_23_08_845Z-debug.log
[1] npm run client:react exited with code 1
--> Sending SIGTERM to other processes..
[0] [nodemon] 1.17.5
[0] [nodemon] to restart at any time, enter `rs`
[0] [nodemon] watching: *.*
[0] [nodemon] starting `node server.js`
[0] npm run server:koa2 exited with code null
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Error GraphQL error: Variable "$topic" got invalid value "1"; Expected type Int; Int cannot represent non-integer value: "1"