CSS Assets

[ryanflorence]

A lot of clientside stuff has need of assets for the script (like a UI library).

Perhaps define "assets" in the package.json, then have ender pull them out of node_modules and toss them into an assets directory?

[ded]

this is a great idea. i think we're looking into keeping everything tucked into the "ender" key so we're not populating packages with too many non-nodish things. with that said, we want to support the ability to pass in an options hash ...

"ender": {
  main: "path/to/main.js"
  , "other": "stuff"
  , "assets": "path/to/assets"
}

[fat]

I was looking through the package.json spec and actually i think the best place to put this particular thing would be the directories key... so it would look like:

{
  "name": "fat",
  "version": "0.0.1",
  "authors": ["Jacob Thornton <@fat>"],
  "keywords": ["ender", "events", "event"],
  "main": "./fat.js",
  "ender": "./src/bridge.js",
  "directories": {
    "assets": "src/assets"
  }
}

[ryanflorence]

That looks good to me with a couple questions:

1. Does ender just assume you want the assets directory packaged up?
2. Is this flexible enough? What if I've got two assets directories I want packaged up?

[ded]

does ender just asume you want the assets directory packaged up?

perhaps..

$ ender build foo bar --noassets

or

$ ender build foo bar --includeassets

what if i've got two assets directories i want packaged up?

"directories": {
  "assets": ["src/a/assets", "src/b/assets"]
}

[fat]

That's a good question... i'm starting to think we should limit the options (so we don't get options crazy like git). Less to learn i think is nice... What if we just pause the build process when we encounter an assets dir? We could ask if a user wants to include the dir for a specific package and we could also ask where they would like to put it.

[ryanflorence]

I'd rather be scriptable and option crazy, than non-scriptable.

$ ender build foo --noassets

Would be my vote (or maybe --nobooty but I digress). Seems like if a script has assets, and ender is building, you should get the assets by default.

[ded]

the other question is, where do those assets go? how does one publish them? (because they won't be able to live on NPM)

[fat]

yeah they do/will... thats why we would use the directories key... we would just have to relocate them somewhere...

[jasonkuhrt]

Same issue here? #84

[rvagg]

ref #131