Multiple unmet peer dependencies during yarn build

[MikeTheCanuck]

2nd step of build procedure is to run yarn command. On my system it results in the following warnings:

$ yarn
yarn install v0.20.3
[1/4] 🔍  Resolving packages...
[2/4] 🚚  Fetching packages...
[3/4] 🔗  Linking dependencies...
warning "chai-enzyme@0.6.1" has unmet peer dependency "chai@3.x".
warning "chai-enzyme@0.6.1" has unmet peer dependency "enzyme@1.x || 2.x".
warning "chai-enzyme@0.6.1" has unmet peer dependency "react-addons-test-utils@^0.14.0 || ^15.0.0-0".
warning "react-selectize@2.1.0" has unmet peer dependency "react-addons-css-transition-group@^0.14.0 || ^15.0.0".
warning "react-selectize@2.1.0" has unmet peer dependency "react-addons-shallow-compare@^0.14.0 || ^15.0.0".
warning "sinon-chai@2.8.0" has unmet peer dependency "chai@>=1.9.2 <4".
warning "sinon-chai@2.8.0" has unmet peer dependency "sinon@>=1.4.0 <2".
[4/4] 📃  Building fresh packages...
warning Your current version of Yarn is out of date. The latest version is "0.21.3" while you're on "0.20.3".
info To upgrade, run the following command:
$ curl -o- -L https://yarnpkg.com/install.sh | bash
✨  Done in 214.92s.

Unclear whether such warnings can be ignored for this project - the subsequent yarn go command cascade ultimately results in the following error:

ERROR in ./civicApp/routes/CivicApp.js
Module not found: Error: Can't resolve '@hackoregon/react-component-library/lib/Navigation/Header' in '/Users/mike/code/~hackoregon/civic-server/example/civicApp/routes'
 @ ./civicApp/routes/CivicApp.js 11:14-82
 @ ./civicApp/routes.js
 @ ./civicApp/client.js
 @ multi app
error Command failed with exit code 2.

[DavideDaniel]

The warnings are emanating from the link created for @hackoregon/react-component-library - until we actually publish to npm, installing via github pulls in the devDependencies as well which results in those warnings. However, Yarn doesn't seem to be linking the package correctly, so doing a regular npm install instead of yarn will work for you.

[MikeTheCanuck]

OK, if doing a regular npm build will generate the output that we'll need (to land on S3?), then could you or someone please help me figure out what it means to do a "regular npm build"? I unfortunately have no background to fill in that gap. Thanks!

[DavideDaniel]

Sorry Mike.. I just meant npm install instead of yarn install