Add component.json?

[markreg]

I believe the repo had a component.json file a while back. Was there a reason for removing it?

[markreg]

Should I make a pull request or was it left out intentionally?

[eivindfjeldstad]

The problem is that the code base has been split into several modules, most maintained by @get, none of which has a component.json. The one in this repo was outdated for months before being removed. I assume it means component will no longer be supported, but i afaik @guille hasn't confirmed this yet :)

[rauchg]

engine.io-client, like many other modules in the JavaScript ecosystem, runs on both the Node.JS and browser environments.

We already have a manifest file that describes the module name, its version, its description, its dependencies… I've come to realize that duplicating all of that into a new file called component.json is not the best idea.

Two things can address your particular need:

1. component(1) embraces the possibility of leveraging NPM modules without having authors add a new manifest
2. you compile package.json down to component.json programmatically

Ultimately, since with browserify this module works fine, the second option is totally technically viable if the component maintainers are not interested in the first one.

I think it'd be unfair for me to maintain component.json and keep out bower.json (like I have in the past). Instead, I take the (what I consider) sane approach of not duplicating manifests in source control.