Remove requirement for composes to be the first thing

[tivac]

Feature Use Case

The current behavior of requiring that composes be the first property comes directly from the CSS Modules Spec:

There can be multiple composes rules, but composes rules must be before other rules.

This made a lot of sense at the time, but there's no technical need for that requirement in modular-css (in fact if we removed it I could delete a bunch of code that enforces the requirement) and there's better tools for specifying very explicit property ordering now like stylelint-order.

Feature Proposal

Remove the logic that enforces that composes be the first property in a declaration, and update the guide on the site to remove any references to the requirement & list it as another divergence from CSS Modules

[tivac]

Haven't seen any serious concerns when chatting about this, so working on it now.