Make name optional in bower.json

[cowboy]

I'm not sure if any other published-package-centric fields are required in bower.json, but at the very minimum, the name field should be optional. The name field should, however, be required for publishing a package.

There was a (now resolved) issue isaacs/npm#914 to make name and version in package.json optional, because many projects that utilize npm are never published. They use npm modules solely as dev dependencies, and package.json solely as a place to store the list of dev dependencies.

[sindresorhus]

👍

[klzns]

+1

[franciscolourenco]

+1

[vladikoff]

Plus One

[cowboy]

Did this ever get fixed? I saw that #1065 (duplicate?) was recently closed.

[benschwarz]

Ultimately, this should be tracked in the bower.json-spec repo -https://github.com/bower/bower.json-spec/blob/master/README.md as you'll see, name is currently still required.

I tend to think a name should always be used, whether the package is published or not.

[sheerun]

I think we can use internally directory name if name is not provided.

Scheduling on 1.4.0.

[gerardroche]

There is an open issue on the spec repository about this bower/spec#22.

Also one about the version being optional bower/spec#4

[jmshal]

👍

[vsn4ik]

👍 for add private option.

[sheerun]

I think it was implemented at some point