Deprecations & Errors in initial `npm install`

[richb-hanover]

Using commit 8e4c2e1 (Feb 2016): npm install gave several kinds of warnings/errors. Are these known? Will they be fixed? Are they important? Thanks!

npm WARN deprecated [email protected]: Babel's CLI commands have been moved from the babel package to the babel-cli package
npm WARN deprecated [email protected]: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated [email protected]: ReDoS vulnerability parsing Set-Cookie https://nodesecurity.io/advisories/130
npm WARN prefer global [email protected] should be installed with -g

And also...

WARNING in bundle.5dde88166bbba175a25c.min.js from UglifyJs
Condition always true [./~/react/lib/ReactMount.js:764,0]
Condition always true [./~/react/lib/findDOMNode.js:46,0]
Condition always true [./~/react/lib/instantiateReactComponent.js:80,0]
Dropping unreachable code [./~/react/lib/shouldUpdateReactComponent.js:40,0]
Condition always true [./~/react/lib/traverseAllChildren.js:158,0]
Side effects in initialization of unused variable REQUEST_KITTENS [./client/actionTypes/kittens.js:1,13]
Side effects in initialization of unused variable REQUEST_KITTENS_SUCCESS [./client/actionTypes/kittens.js:2,13]
Side effects in initialization of unused variable REQUEST_KITTENS_ERROR [./client/actionTypes/kittens.js:3,13]
Side effects in initialization of unused variable ADD_KITTEN [./client/actionTypes/kittens.js:5,13]
Side effects in initialization of unused variable ADD_KITTEN_SUCCESS [./client/actionTypes/kittens.js:6,13]
Side effects in initialization of unused variable ADD_KITTEN_ERROR [./client/actionTypes/kittens.js:7,13]
Side effects in initialization of unused variable DELETE_KITTEN [./client/actionTypes/kittens.js:9,13]
Side effects in initialization of unused variable DELETE_KITTEN_SUCCESS [./client/actionTypes/kittens.js:10,13]
Side effects in initialization of unused variable DELETE_KITTEN_ERROR [./client/actionTypes/kittens.js:11,13]
Side effects in initialization of unused variable invokeReturn [./~/babel-regenerator-runtime/runtime.js:167,0]
Side effects in initialization of unused variable invokeReturn [./~/babel-runtime/regenerator/runtime.js:190,0]
Condition always false [./~/babel-runtime/regenerator/runtime.js:46,0]
Condition always true [./~/react/lib/ReactDOMComponent.js:907,0]
Dropping side-effect-free statement [./~/react/lib/ReactEventListener.js:72,0]
Dropping unused function handleTopLevelWithPath [./~/react/lib/ReactEventListener.js:98,0]
Dropping unused variable DOCUMENT_FRAGMENT_NODE_TYPE [./~/react/lib/ReactEventListener.js:26,0]

[only-entertainment]

These are likely the output of the .eslint checks and are configurable. During the compilation of JSX the compiler is throwing warnings about dead variable stores and unused code paths.