Enderfile

[devth]

I think it'd make more sense to specify packages you want under an Enderfile of some sort, then ender install to satisfy deps. The current node_modules doesn't seem like it should go in my git repo. I'd be happy to take a stab at it.

Also, Enderfile sounds cool.

[ded]

hmmm

[fat]

you can do this already with a package.json. Add node_modules to your .gitignore and add something like this https://github.com/ender-js/jeesh to your project root.

[devth]

Cool. This can't support multiple output files in the same project can it? For example, I have a rails 3.1 app that has 3 separate templates which all need their own unique JS deps. I'd like to output 3 ender.js's:

app/assets/javascripts/application/ender.js
app/assets/javascripts/display/ender.js
app/assets/javascripts/mobile/ender.js

[fat]

oh, not currently.

[devth]

Ok, so if I were to implement this idea, would you prefer it to live in package.json or do you like the idea of an Enderfile?

package.json might be limiting (I'm not sure the spec would even support my idea), and I don't intend to actually publish the "package" anywhere. It's just a deps spec for my specific app.

[fat]

I'd prefer it to live in a package.json. We've been meaning to extend the ender keyword to support an object syntax. However, I think one possible way to make this work for you would be to make the ender param accept an array as well.... so you would do something like:

ender: [{ output: './public/js/ender-1', dependencies: {...}, { output: './public/js/ender-2', dependencies: {...}, }]

[devth]

Cool. I'll play with this idea (unless you beat me to it).

[fat]

Alternatively, with the current ender code you could define multiple packages for your different ender builds and use -o to output them to different locations.

[rvagg]

ref #131