spec

spec copied to clipboard

Add tmp config to object, as some systems do have `/tmp` access :S... And we spent some time to figure out that `tmp` can be set but didn't see as...

jeremyrajan

`name` should only be required for published packages

22

`name` should only be required for published packages. In example, both [composer](https://getcomposer.org/doc/04-schema.md) and [npm](https://www.npmjs.org/doc/files/package.json.html) only require a name for published packages. See also _version attribute should always be required_ #4

gerardroche

We have a Jenkins server running a multibranch job. When a release is finished in the repo (gitflow), develop and master branches are updated. The multibranch job is triggered, starting...

raphaelquati

files: list all required files for build tools

71

Since resolving `main` in #43, we've thrown a wrench in the gears for build tools, most prevelantly [Wiredep](https://github.com/taptapship/wiredep). Wiredep needs a list of all the files to be included when...

desandro

They're listed on https://bower.io/docs/config/ but not doc'd in this spec.

csells

I would like to see the Bower spec be more specific about what should go in the author field. I agree in the demarcation outlined in #15, but if you...

Anthropic

Solves https://github.com/bower/bower/issues/1229

sheerun

main property for es6 module version

1

In npm, you can have both main and esnext:main property in package.json. This is handy when your module have different build output for es5 and es6. Does bower.json plan to...

dfahlander

Version the spec itself

5

The spec itself ought to be versioned, and a field should be added to `bower.json` indicating at least the major (and perhaps also the minor) version of the `bower.json` spec...

cvrebert

Add the possibility to host custom fields in the bower.json

5

I would like to have the possibility to add custom fields in the bower.json. Maybe there could be a 'custom' key within the specification?

ivan-saorin