Thanks for the heads up! If I'm understanding right, is this the general idea for a package:

// bower.json
{
  "name": "my-package",
  "main": "index.js",
  "files": [
    "index.js",
    "css/styles.css",
    "fonts/font.ttf"
  ],
  "dependencies": {
    "jquery": "*"
  }
}

$ bower list --files
{
  js: [
    "jquery/jquery.js",
    "my-package/index.js"
  ],
  css: [
    "my-package/css/styles.css"
  ],
  ttf: [
    "my-package/fonts/font.ttf"
  ]
}

Bower would need the user to define files, otherwise the output from bower list --files would just include the main file? And if the new standard wasn't adopted by a package author (say, main is still an array), would the output include all of those paths?

I know I made some assumptions here, I'm just trying to figure out how the tooling ecosystem could continue to have all of the information needed in relation to ordering/reference injection. Please correct me if I'm going too far off track :)

You have the basic idea. The Bower team still needs to settle on the files specification. But the idea is that it would contain all the files build tools like Wiredep puts together. I'll reach out again once we're ready.

No problem, thanks for keeping us in the loop.

@desandro is there any movement on the files spec? The issues linked above show some of the problems users are having now that some larger packages are following the new main spec.

I'll look to make some moves next week

@stephenplusplus Opened bower/spec#47 to resolve this issue. Would love to get input on what would work best for Wiredep.

...should probably have decided on/accepted the files issue before finishing main...