bower list doesn't list full dependency tree

[passy]

If you run bower list in a directory with a component that has their own dependencies, the output depends on whether you have the main dependency saved in your bower.json or not. I talked to @satazor about this and we agreed that this behavior is a little counter-intuitive.

Example

If you're in an empty directory and run bower install imagesloaded && bower list, you get the complete dependency tree:

├── eventEmitter#4.2.0 extraneous
├── eventie#1.0.3 extraneous
└─┬ imagesloaded#3.0.1 extraneous
  ├── eventEmitter#4.2.0
  └── eventie#1.0.3

If you, however, save the dependency with bower install --save imagesloaded && bower list, you only see the top-level dependency:

└── imagesloaded#3.0.1

If you for instance rely on the this to include the dependencies in your HTML, you need the full output. It should be mentioned, that bower list -p does list all dependencies in both cases.

[satazor]

@passy With bower.1.0.0-alpha.7:

bower install --save imagesloaded && bower list:

$ bower list
bower check-new     Checking for new versions of the project dependencies..
foo /Users/satazor/Work
└─┬ imagesloaded#3.0.1
  ├── eventEmitter#4.2.0
  └── eventie#1.0.3

Though, when a bower.json file is not presented there's no feasible way to make them nested unless we add an internal prop to the package meta(.bower.json) file saying that imagesloaded was installed directly and not as a dependency of another.
Will look at this later tonight.