Making @best/cli leaner

[pmdartus]

Observations

When installing for the first time @best/cli I noticed that it takes around 20 sec. I also realized @best/cli pull-down 151 MB worth of NPM dependencies.

When looking at the generated yarn.lock you can observe that @best/cli it possible to see that some projects like webpack or jest are also pulled down. When running npm ls --json that out of the 3159 dependencies listed, 2508 are pulled down by the @best/frontend.

Is it possible to make the @best/cli dependency on @best/frontend optional?

Reproduction steps

mkdir test
cd test
yarn init -y
yarn add -D @best/cli

Versions

• node: 10.16.0
• best: 4.0.0-alpha4

[jasonsilberman]

I think what we can do is remove the dependency on the frontend, as it is only used when a user tries to generate the static HTML frontend. So we can require that a user list that as a peer dependency when they want to use that feature.