You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 30, 2018. It is now read-only.
It has been the source of some confusion that the repo is called cli-build but the package is called cli-build-webpack.
I think we should isolate ourselves from a specific implementation (in this case webpack) and rename the repo to cli-build-app and use this name for the published package.
The text was updated successfully, but these errors were encountered:
When you say, "build widgets", do you mean generate a new widget? If that is the case, then I would implement that via a dojo create widget command and leave cli-build as it is (and remove the -webpack suffix from the package name).
So the aim of the rename is to have parity between the repo name and the package name on npm.
This has already caused some confusion with beta users in the community.
Yes, I understood that. My question is why not use cli-build for both? If building a single widget consists of generating output for a limited set of files, I do not see why that should require an entirely separate package.
All of our CLI commands follow the same format, irrespective of them being tied to a particular technology. Wouldn't this one be best named cli-build-project even though most users would only have use dojo build as far as we have plans at the moment?
It has been the source of some confusion that the repo is called
cli-build
but the package is calledcli-build-webpack
.I think we should isolate ourselves from a specific implementation (in this case
webpack
) and rename the repo tocli-build-app
and use this name for the published package.The text was updated successfully, but these errors were encountered: