Vyriy Stylelint Config

@vyriy/stylelint-config is a shared Stylelint configuration package for Vyriy projects.

The goal of this package is to keep CSS and SCSS linting consistent across applications, libraries, examples, and internal packages. Instead of copying the same Stylelint rules into every project, each package can reuse the shared Vyriy configuration.

This keeps styles predictable, easier to review, and safer to maintain as the project grows.

Installation

Install the shared config together with Stylelint:

yarn add @vyriy/stylelint-config stylelint

Basic usage

Create a stylelint.config.mjs file in the project root:

export { default } from '@vyriy/stylelint-config';

This file re-exports the shared Vyriy Stylelint configuration and makes it available to Stylelint in the current project.

Example SCSS file

Create a styles.scss file with an intentionally broken SCSS block:

a {
  color: red;

The block is not closed with }, so Stylelint should report a syntax error.

Run Stylelint

Run Stylelint for the SCSS file:

npx stylelint styles.scss

Output:

styles.scss
  1:1  ✖  Unclosed block  CssSyntaxError

✖ 1 problem (1 error, 0 warnings)

Stylelint correctly detects that the a selector block is not closed.

Fixed SCSS file

After closing the block, the file becomes valid:

a {
  color: red;
}

Run Stylelint again:

npx stylelint styles.scss

If there are no problems, Stylelint finishes without error output.

Why shared Stylelint config?

A shared Stylelint config helps keep styling rules consistent across multiple packages and workspaces.

For Vyriy projects, this is useful because styles may exist in different places: UI libraries, examples, documentation, blog components, or application workspaces. A common config makes all of them follow the same baseline rules.

The result is a calmer styling workflow: fewer local decisions, fewer duplicated configs, and more predictable code reviews.

Documentation

See the Stylelint config API documentation.