It's because people are depending on internals of bower, like
"bower/lib/renderers/StandardRenderer"
Instead we move templates and bin to lib directory and leave
paths intact. Additionally we alias bin/bower to lib/bin/bower.
They caused more issues than useful they were.
Instead, we'll focus on fetching statistics from
NPM registry to watch Bower's popularity, and
GitHub stars over time to watch packages' popularity.
This is almost certainly not trying to replace 's' characters in a command and is, instead, meant to check for nested properties on bower.commands that were not found in bower.abbreviations for some reason. The kicker is that bower.abbreviations already contains the full command names in addition to the shortened ones, so this code path ("Direct lookup") probably never actually results in finding anything and can probably safely be removed.
The user is prompted with a question whether he would like to provide usage data
on the first start, when run in interactive mode. The current implementation
tracks calls to `install`, `info`, `search` and `uninstall` when run with at
least one parameter.
Fixes#260
Closes gh-796.
- Add search command
- Cache clean now clears the registry cache
- Fix error when accessing an unknown deep command in the cli
- Change from 'roaming' to 'path' in the config
- Change from 'canonicalPackage' to 'canonicalDir'
- Fix dev dependencies of nested packages being fetched
- Ignore invalid installed packages
- Various cache fixes and improvements
- Fix .bower.json being deleted if a package specified ignorables
- Use fstream instead of ncp to solve the EMFILE errors
- Fix cache clean command
- Lots of improvements and fixes of the Manager
- Only save json if the contents changed
- Add nom like tree to installed/updated packages
- Fix help usages.
This was an huge commit.
- Allow nested commands
- Switch resolve cache in memory object cache to LRU
- Store non-semver packages in the cache
- Tweak help messages
- Various fixes and tweaks
