Add buildDependencies to package.json

I think it's time to move build dependencies out of devDependencies to a separated group. It could be named "buildDependencies".

Motivation

Development dependencies contain tools like Eslint, Webpack development server, static server and many others which isn't required on a build stage. This affects the final installation size and increases the time updated code spends in CI/CD. Also it creates extra load on disk and network to download and store megabytes of redundant code.

Also it lets developers to create all-in-one packages which contain build and development tools simultaneously. What affects the size of this packages.

Pros

• Faster CI/CD.
• More compact installations.
• Costs reduction.

Cons

• Such solution requires separation of build and dev configuration files for tools like Gulp or Grunt to avoid dependencies import issues.
• Requires Yarn, PNPM and NPM implement this feature all together.
• Requires learning to use new option or automation to prevent dependency misplacement.

Start by reviewing the package.json dependency groups and the issue's discussion of Yarn, PNPM, and NPM support. Determine whether the proposed buildDependencies group has an agreed design and what coordinated package-manager changes would be required; done means a settled specification and implementation path rather than a single repository edit.