matches-selector published to npm (at least) 3 times

[timoxley]

@visionmedia @azer @ForbesLindesay can we sort out this madness please?

component/matches-selector is now published on npm in 3 different variants:

• matches-dom-selector
• matches-selector
• matches-selector-2

From these 3 repos:

• https://github.com/ForbesLindesay/matches-selector
• https://github.com/azer/matches-dom-selector
• https://npmjs.org/package/matches-selector-2

They're all (mostly) the same damn code.

Now I'm sure this happened because everyone needed a solution asap, I'm not suggesting anyone screwed up, but can we take a moment to detangle?

Ideal solution (please guys):

azer:

1. unpublish matches-dom-selector

ForbesLindesay:

1. unpublish matches-selector

visionmedia:

1. Unpublish matches-selector-2
2. Add the package.json from matches-selector-2 to component/matches-selector
3. Rename name 'matches-selector-2' in package.json:
4. republish to npm under matches-selector name
5. Consider adding @ForbesLindesay & @azer as collaborators on component/matches-selector to maintain the package.json for browserify/npm compatibility.

Reasonable request?

[jonathanong]

@ForbesLindesay is already an org member so he should be able to do it himself.

[azer]

I think there is a dependency missing in NPM (should be query). Which was my reason to publish my own

[ForbesLindesay]

I inlined query in my version because the code to just do it directly was shorter than the code to use an additional module. I'm happy to collaborate with other people to maintain my branch. I don't have any real intentions to deviate from this module's API, but the dependency on query is silly and just trying to make a point, so I'm not going to change that.

[azer]

@ForbesLindesay query dependency isn't silly if your app supports IE8 etc.

[tj]

+1 but doesn't really matter to me I don't use any of them out of npm now

[timoxley]

@visionmedia does that mean you're actually using component for real now?

[tj]

yup!

[timoxley]

cool, so can we get a resolution here? If you insist on keeping a fork for the sake of removing a single dependency (I'm not really sure why it's important to remove it?) perhaps @ForbesLindesay and @visionmedia could swap repo names so the 'official' repo doesn't have the trailing -2? possible?

[jonathanong]

@azer http://caniuse.com/#feat=queryselector http://caniuse.com/css-sel3 you only need query if you're using css3 selectors and such, which i personally never use to match

[tj]

sounds good to me, you could always use "component/matches-selector" in npm but then you're stuck with git

[TooTallNate]

Any update on this one? Seems like it should be pretty easy to resolve.