[tjsix]

Maybe it's just me but having no manifest makes using this tool quite painful. It has taken me 10 mins just to figure out how to structure the require()'s so that it doesn't error out, and that's with only requiring two packages.

For example I created a quick index.js file and required angular and restangular. It immediately errored out because the angular.js repo doesn't use semver on it's master branch. Ok fine, switch to angular/bower-angular, nope, it looks for index.js so my require now has to read: require('angular/bower-angular:angular.js'). Run again, error, same issue with restangular, it's looking for index.js. That require now reads: require('mgonto/restangular:dist/restangular.js'). I had to actually find where the files are that I wanted to require and explicitly state them in the require. Shouldn't this automatically parse bower/component/package.json files for this info, especially if you're touting the 'No Manifest' thing.

[anthonyshort]

index.js as the entry point for a module is pretty standard with projects built around Component and npm. It's bower and the lack of the standard there that creates the issue.

[bakareika]

As an author of a (small) number of npm+bower packages I must admit that nope, that's not "standard" in any meaningful way.

[TheHydroImpulse]

It's definitely standard in Node land and also Component(1). Bower, on the other hand, does not and thus is the culprit.

[skeoh]

index.js is only 'standard' in node insofar as it is the fallback entry point if a package.json file is not found or does not specify a 'main' file.

[lobster_johnson]

It's only moderately common. Just took a look at a project of ours, and of 565 packages, only 261 (46%) had an index.js.