Skip to content
#

postcss

Here are 2,318 public repositories matching this topic...

stylelint
ilyub
ilyub commented Dec 20, 2021

What is the problem you're trying to solve?

I guess that selector-max-universal is performance related rule.
I.e. it is supposed to forbid patterns that hit perfomance.

Consider the following patterns (with selector-max-universal = 1):

  1. "*" involves O(N) search. So, it is Good.
  2. "* *" involves O(N^2) search. So, it is Bad.
  3. "* + *" involves O(N) search ("+ *" = next element = it
status: ready to implement type: new option good first issue

🚀 Boilerplate and Starter for Next.js 12+, Tailwind CSS 3 and TypeScript ⚡️ Made with developer experience first: Next.js + TypeScript + ESLint + Prettier + Husky + Lint-Staged + VSCode + Netlify + PostCSS + Tailwind CSS

  • Updated Mar 23, 2022
  • TypeScript

Improve this page

Add a description, image, and links to the postcss topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the postcss topic, visit your repo's landing page and select "manage topics."

Learn more