Need to suppress/resolve Meteor warnings in console

[kmcculloch]

From @b5 on February 2, 2017 13:40

Just looks bad to all our friends who start to poke around with the app :)

Copied from original issue: b5/pipeline#19

[kmcculloch]

Assuming that these are the warnings in question:

"WARNING: npm peer requirements not installed:

• react@15.4.2 installed, react@0.14.x needed
• react-dom@15.4.2 installed, react-dom@0.14.x needed
• react-addons-transition-group@15.4.2 installed, react-addons-transition-group@0.14.x needed
• react-addons-css-transition-group@15.4.2 installed, react-addons-css-transition-group@0.14.x needed
• react-addons-linked-state-mixin@15.4.2 installed, react-addons-linked-state-mixin@0.14.x needed
• react-addons-create-fragment@15.4.2 installed, react-addons-create-fragment@0.14.x needed
• react-addons-update@15.4.2 installed, react-addons-update@0.14.x needed
• react-addons-pure-render-mixin@15.4.2 installed, react-addons-pure-render-mixin@0.14.x needed
• react-addons-test-utils@15.4.2 installed, react-addons-test-utils@0.14.x needed
• react-addons-perf@15.4.2 installed, react-addons-perf@0.14.x needed

Read more about installing npm peer dependencies: http://guide.meteor.com/using-packages.html#peer-npm-dependencies "

This took a crapload of grepping to track down. First of all, the error itself isn't generated out of a package.json in any of the dependencies, but via a plugin:

https://github.com/tmeasday/check-npm-versions/blob/master/check-npm-versions.js

The package with the offending "checkNpmVersions" call is react-runtime:

https://github.com/meteor/react-packages/blob/react%400.14.6/packages/react-runtime/react-runtime.js

This nonsense goes away on the 15.0.0 branch of that package:

https://github.com/meteor/react-packages/blob/react%4015.0.0/packages/react-runtime/react-runtime.js

So I installed it:

meteor add react-runtime@15.0.0 --allow-incompatible-update

...and committed the new .meteor package info to a new branch, peer-dependency-errors. So far the app is running on my localhost without the annoying log messages and without any (new) errors. This did cause a couple of other changes to the meteor package specifications that @b5 or someone with more advanced meteor knowledge should review.