:matches(element)

[stevenvachon]

.class {
  &:matches(element) {
    property: value;
  }
}

produces:

.classelement {
  property: value;
}

when it should produce:

element.class {
  property: value;
}

[MoOx]

Looks like a bug indeed. Feel free to report it here https://github.com/postcss/postcss-selector-matches.
PR welcome!

[MoOx]

Closed by postcss/postcss-selector-matches#8

[yordis]

@MoOx Can you update the release on the other package I want to add some regression testing in this package

[MoOx]

No need to do it. No need to duplicate a test ;)

[yordis]

@MoOx isn't duplicate testing. Remember that we created the regression testing for see how it works with every feature enabled.

How do we know that this doesn't break integrated with the other features.

[MoOx]

cssnext don't cover all possibilities of packages used. And I guess most packages don't cover all use case of they libraries they used...

[yordis]

@MoOx that's why we could use this regression for check that IMO. The idea is not go crazy and add every single use case but at least the one we know should pass after fixed them.

[MoOx]

We don't need a release for this fix. Our current usage of postcss-selector-matches will get all patch release automatically. postcss-selector-matches 2.0.2 is out, so just reinstall postcss-cssnext and it should be good for you.