best-cli module needs to be moved into the @best scope

[a-hoff]

best-cli module should be moved into the @best scope along with the rest of the best packages.

An npm package that consumes best will have a .npmrc file with the following in it:
@best:registry=https://npm.lwcjs.org

which allows the private registry to be used to get the best packages. However this doesn't work for best-cli because it is not in the @best scope.

As a current workaround, a consumer has to directly put the URI of the tarball in their package.json dependencies map.

[diervo]

I would love to, but I need to claim the @best scope first so we can open source it eventually

[a-hoff]

We can move this into the @best scope in the private npm.lwcjs.org repository where the other best modules already exist right?

[alrra]

For the public registry, it seems @diervo has the best package, but @best is already claimed by someone.

[pmdartus]

@diervo Let's change the name =)

[jasonsilberman]

@best/cli is live with an alpha of v4.