Update Dependencies

[tech4him1]

Currently, many of the CMS' dependencies (dev and normal) have updates available (use yarn outdated). We should probably go through them and determine which should be updated, and which should not. This issue will track progress.

Related to #542, #589.

Separate Issues: #478, #413, #664.

[tech4him1]

• The CMS' node-sass version does not support Node v8. SASS is no longer needed with [email protected].
• autoprefixer should be updated to add/remove browser prefixes.

[tech4him1]

React depreciations: prop-types and react-create-class will need to be installed as separate packages.

Done in #590.

[tech4him1]

Current Yarn warnings (w/[email protected]):

• warning "[email protected]" has incorrect peer dependency "prop-types@^15.5.9".
• warning "[email protected]" has incorrect peer dependency "prop-types@>=15.5.0".
• warning "[email protected]" has incorrect peer dependency "prop-types@^15.5.7".
• warning "[email protected]" has incorrect peer dependency "react-transition-group@^1.1.3".

Also yarn has some peer-dependency errors from yarnpkg/yarn#2688 and yarnpkg/yarn#2387 that we don't need to worry about too much -- so some of the warnings Yarn outputs are not valid. This bug will be fixed in Yarn 1.1.0, see yarnpkg/yarn#4478.

[tech4him1]

So for dependency updates, I'm thinking of going through two stages:

1. Upgrade packages that are currently giving depreciation warnings (or are no longer supported and might break things).
2. Figure out if we want to upgrade any major versions that are still working (react-router, etc.).

Thoughts?

[erquhart]

@tech4him1 sounds like a plan.

[tech4him1]

Dependency updates will be split into three categories:

1. UI dependencies. (React, Redux, Notifications) These should be really easy to test -- either the UI is broken or it is not.
2. Dev dependencies. (WebPack, Babel) These are fairly easy to test whether they break something or not, we'll just need to watch the transpiler's output.
3. Backend/Internal dependencies. (gotrue-js, uuid) These will need fairly intensive testing to make sure that they still work for everybody.

[tech4him1]

OK, I think the bulk of this is done. @erquhart @Benaiah are you good with me closing this?

[erquhart]

Agreed.