search

linemanjs / lineman-browserify

A Lineman plugin that configures Browserify for you
6 stars 5 forks source link

does entrypoint.{js,coffee} filename break browserify convention? #9

Open jasonkarns opened 10 years ago

jasonkarns commented 10 years ago

@searls and I discussed potentially naming the entrypoint file after the project (via <%= pkg.name %>)

Was this postponed or intentionally avoided?

searls commented 10 years ago

I forgot and then I shipped it

On Thu, Feb 27, 2014 at 5:27 PM, Jason Karns notifications@github.com wrote:

@searls and I discussed potentially naming the entrypoint file after the project (via <%= pkg.name %>)

Was this postponed or intentionally avoided?

Reply to this email directly or view it on GitHub: https://github.com/linemanjs/lineman-browserify/issues/9

jasonkarns commented 10 years ago

Anybody else have experience with this convention (or lack thereof)? / ping @davemo

Based on reading, it appears to be a convention to use the package/project name as the entrypoint file under lib/. But it doesn't appear to be a strong convention. If it's not that common, perhaps we should keep the filename default as entrypoint.{js,coffee}.