npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@perplex-digital/stylelint-config

v18.0.0

Published

Order and Concentric-based property sorting for Stylelint.

Readme

Perplex CSS Order & Property Sorter

npm version npm downloads github issues

🗂️ A heavily opinionated Stylelint config that:

  • Supports linting .vue files
  • Orders CSS the way Perplex does
    • Supports Tailwind 4 directives like @apply and @variant
  • Sorts CSS properties the way Concentric-CSS did but with:
    • 'Box sizing' and 'Overflow' modules above the 'Box model - Margin' module
    • outline grouped with the 'Borders' module
    • 'Backgrounds and box-shadow' module below the 'Box model - Padding' module
    • 'Positioning' and 'Anchor positioning' modules above the 'Transforms' module

Usage

  1. Add stylelint and this package to your project:
    pnpm add stylelint @perplex-digital/stylelint-config
  2. Configure your stylelint configuration file to extend this package:
    export default {
        extends: ['@perplex-digital/stylelint-config'],
        rules: {
            // Add overrides and additional rules here
        },
    };

Advanced

The default setup applies these rules:

  • stylelint-config-standard
  • @dreamsicle.io/stylelint-config-tailwindcss
  • stylelint-config-recommended-vue (including stylelint-config-recommended and stylelint-config-html)
  • @stylistic/stylelint-plugin,
  • stylelint-use-logical-spec
  • stylelint-high-performance-animation
  • Some overrides of these rules
  • order/order with the Perplex order.
  • order/properties-order with the various property groups. If you need to configure other options for this rule, the groups can be imported separately and the rule configured to your needs.
import propertyGroups from '@perplex-digital/stylelint-config/property-groups';

export default {
    extends: [], // Do not extend the config here.
    rules: {
        // Configure the rule manually.
        'order/properties-order': propertyGroups.map((group) => ({
            ...group,
            emptyLineBefore: 'always',
            noEmptyLineBetween: true,
        })),
    },
};

Releasing

Releases are automated with Changesets and GitHub Actions.

  1. Create a branch from develop and make your changes. Commit messages must follow Conventional Commits (enforced by commitlint).
  2. Add a changeset for every user-facing change:
    pnpm changeset
    Pick the bump type (patch, minor, major) and write a short summary; it ends up in the changelog and release notes. Commit the generated .changeset/*.md file. A pre-commit hook blocks commits that touch src/ without a new changeset.
  3. Open a pull request into develop. CI runs pnpm lint and pnpm test.
  4. When ready to release, create a release/vX.Y.Z branch from develop and open a pull request into main. After merging, the release workflow opens (or updates) a "Publish release" PR that bumps the version and updates CHANGELOG.md.
  5. Merge the "Publish release" PR. The workflow then publishes to npm, pushes the git tag and creates a GitHub release with the changelog as release notes.
  6. The workflow automatically merges main back into develop so it has the version bump and changelog.

Publishing uses npm trusted publishing (OIDC), so no npm token is needed. The trusted publisher is configured on npmjs.com for the release.yml workflow.

References

@mdo on CSS Property Order