Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

Question: Is `component.json` required? #37

Closed
jdalton opened this Issue Sep 12, 2012 · 7 comments

Comments

Projects
None yet
5 participants
Contributor

jdalton commented Sep 12, 2012

I noticed that several projects in bower.herokuapp.com/packages don't have component.json files. Is this really needed for say something like Lo-Dash?

My main concern is that I let the package system know that I have a development and production version lodash.js and lodash.min.js.

Owner

sindresorhus commented Sep 21, 2012

// @fat

Contributor

fat commented Sep 29, 2012

It's required for build tools to know where your main build file is - otherwise bower guesses it's a an index file, but in this case it'll be wrong.

@fat fat closed this Sep 29, 2012

Owner

sindresorhus commented Sep 30, 2012

@fat I know it's been discussed before, but I couldn't find it. Would be really nice to be able to feed a component file directly to bower when registering. Not all projects want component.json and this would be a better solution than having to maintain a fork.

Contributor

fat commented Sep 30, 2012

you could build a new server registry if you'd like - but doing so requires a user model, which you'd also have to add. because you would need to update the component.json for each version etc.

i'm open to it though - you should talk to @maccman and see what he thinks tho

Contributor

jdalton commented Sep 30, 2012

Ok, I added the index.js as it may be useful for other projects and deleted the component.js.

Contributor

necolas commented Mar 26, 2013

You can use bower.json (which we're moving towards as the default) or a custom name referenced in your .bowerrc. Check the Bower README for details.

bitmage commented Mar 26, 2013

Ah cool. Sorry, I deleted my previous comment, as I had thought this was on the lo-dash issues page, and my question was addressed to them.

Yeah, moving away from the component.json conflict is much appreciated. Fighting over the filename just wouldn't be productive. :-)

@bitmage bitmage referenced this issue in componentjs/component Mar 26, 2013

Closed

bower component.json vs. component component.json #78

sheerun added a commit that referenced this issue Jun 10, 2016

Merge pull request #37 from riyadhalnur/update-node-versions-travis
Added newer Node versions to Travis
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment