It has been observed that there are 4 npm installation WARNING received stating depreciated package. Are these depreciated packages required or we can move to suggested packages?
I was installing a new bench using the command bench init dgsol-bench
The installation log is as follows:
==============================================
Updating node libraries…
INFO:bench.utils:npm install
npm WARN deprecated babel-preset-es2016@6.24.1: We’re super 
excited that you’re trying to use ES2016 syntax, but instead of making more yearly presets 
, Babel now has a better preset that we recommend you use instead: npm install babel-preset-env --save-dev. preset-env without options will compile ES2015+ down to ES5 just like using all the presets together and thus is more future proof. It also allows you to target specific browsers so that Babel can do less work and you can ship native ES2015+ to user 
! We are also in the process of releasing v7, so please give Planning for 7.0 · Babel a read and help test it out in beta! Thanks so much for using Babel 
, please give us a follow on Twitter @babeljs for news on Babel, join slack.babeljs.io for discussion/development and help support the project at opencollective.com/babel
npm WARN deprecated babel-preset-babili@0.0.12: babili has been renamed to babel-minify. Please update to babel-preset-minify
npm WARN deprecated babel-preset-es2015@6.24.1: We’re super excited that you’re trying to use ES2015 syntax, but instead of continuing yearly presets , we recommend using babel-preset-env: npm install babel-preset-env. preset-env without options will compile ES2015+ down to ES5. And by targeting specific browsers, Babel can do less work and you can ship native ES2015+ to users ! Also, we are in the process of releasing v7, so give Planning for 7.0 · Babel a read and test it! Thanks so much for using Babel , please give us a follow @babeljs for updates, join slack.babeljs.io for discussion and help support at opencollective.com/babel
npm WARN deprecated babel-preset-es2017@6.24.1: We’re super excited that you’re trying to use ES2017 syntax, but instead of making more yearly presets , Babel now has a better preset that we recommend you use instead: npm install babel-preset-env --save-dev. preset-env without options will compile ES2015+ down to ES5 just like using all the presets together and thus is more future proof. It also allows you to target specific browsers so that Babel can do less work and you can ship native ES2015+ to user ! We are also in the process of releasing v7, so please give Planning for 7.0 · Babel a read and help test it out in beta! Thanks so much for using Babel , please give us a follow on Twitter @babeljs for news on Babel, join slack.babeljs.io for discussion/development and help support the project at opencollective.com/babel
==============================================