News for hackers. Stuff that matters.

A comment on Show HN: Duo – a next-generation package manager for the front end. Parent comment

Re:Show HN: Duo – a next-generation package manager for the ... by anthonyshort on Thursday August 21, 2014 @03:01PM (#8209023)
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.
[ Parent | on HN ]
Re:Show HN: Duo – a next-generation package manager for the ... by bakareika on Thursday August 21, 2014 @03:34PM (#8209152)
As an author of a (small) number of npm+bower packages I must admit that nope, that's not "standard" in any meaningful way.
[ Parent | on HN ]
Re:Show HN: Duo – a next-generation package manager for the ... by TheHydroImpulse on Thursday August 21, 2014 @03:47PM (#8209197)
It's definitely standard in Node land and also Component(1). Bower, on the other hand, does not and thus is the culprit.
[ Parent | on HN ]
Re:Show HN: Duo – a next-generation package manager for the ... by skeoh on Thursday August 21, 2014 @07:43PM (#8210271)
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.
[ Parent | on HN ]
Re:Show HN: Duo – a next-generation package manager for the ... by lobster_johnson on Thursday August 21, 2014 @03:52PM (#8209218)
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.
[ Parent | on HN ]