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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@florian-sanders/vscode-stylelint-prebundled

v1.4.0

Published

Official Stylelint extension for Visual Studio Code

Downloads

81

Readme

Disclaimer & acknowledgement

This repo is a fork of stylelint/vscode-stylelint. All the credits go to the original project since all the code is produced by them.

The goal of this repo is to provide the built & bundled code so it can be used in other text editors that don't implement the VSCode extension API. Currently it is used by the a non official WIP Zed editor extension: zed-stylelint.

Basically this repo contains the whole source code of the VSCode extension + the built & bundled code based on this source code.

vscode-stylelint

[![Testing]> (https://github.com/stylelint/vscode-stylelint/actions/workflows/testing.yml/badge.svg)]> (https://github.com/stylelint/vscode-stylelint/actions/workflows/testing.yml)

The official Visual Studio Code extension for Stylelint

Screenshot of Stylelint errors displayed in VS Code

Notice: 1.x of this extension has breaking changes from 0.x versions, including, > but not limited to, changes to which documents are linted by default. See the migration > section for more information.

Table of Contents

  • Installation
    • [Disable VS Code's Built-In Linters (optional)]> (#disable-vs-codes-built-in-linters-optional)
  • Usage
  • [Migrating from vscode-stylelint 0.x/Stylelint 13.x]> (#migrating-from-vscode-stylelint-0xstylelint-13x)
    • [⚠️ Stylelint 13.x and Prior is No Longer Supported]> (#%EF%B8%8F-stylelint-13x-and-prior-is-no-longer-supported)
    • ⚠️ Stylelint is No Longer Bundled
    • [⚠️ Only CSS and PostCSS are Validated by Default]> (#%EF%B8%8F-only-css-and-postcss-are-validated-by-default)
  • Extension Settings
  • Commands
  • Troubleshooting
  • Licence

Installation

  1. Execute the Extensions: Install Extensions command from the [Command Palette].
  2. Type @id:stylelint.vscode-stylelint into the search form and install the topmost one.

The extension first looks for a copy of Stylelint installed in the open workspace folder, > then for a globally installed version if it can't find one. If neither can be found, it > will not lint any documents.

Read the [extension installation guide] for more details.

Disable VS Code's Built-In Linters (optional)

To prevent both [VS Code's built-in linters] and Stylelint from reporting the same > errors, you can disable the built-in linters in either the [user or workspace settings]> [vscode settings] for the languages you intend to use in your workspace.

<img width="430" alt="Screenshot of duplicate error messages" src=> "https://raw.githubusercontent.com/stylelint/vscode-stylelint/main/media/duplicate.png">

An example of duplicate error messages emitted by both the built-in linter and > vscode-stylelint.

For example, the following entries in .vscode/settings.json would disable the built-in > CSS, Less, and SCSS linters:

"css.validate": false,
"less.validate": false,
"scss.validate": false

Usage

See the Stylelint getting started guide for more information.

Once you create a Stylelint configuration file or configure the Stylelint extension's > settings, Stylelint will automatically validate CSS and [PostCSS]> [postcss extension] documents (those with [language identifiers] css and postcss, > respectively).

<img width="430" alt="Screenshot of UI to select a language identifier" src=> "https://raw.githubusercontent.com/stylelint/vscode-stylelint/main/media/language.png">

You can see or change the current document's language in the bottom-right corner of the > editor window.

Migrating from vscode-stylelint 0.x/Stylelint 13.x

⚠️ Stylelint 13.x and Prior is No Longer Supported

See also: [Stylelint 14 migration guide]

vscode-stylelint 1.x expects to use Stylelint 14 at minimum. Usage with prior versions of > Stylelint is no longer supported. While older versions may continue to work for a while, > you may encounter unexpected behaviour. You should upgrade your copy of Stylelint to > version 14 or later for the best experience.

The syntax and configOverrides options have been removed from Stylelint 14 and this > extension. See the [following section]> (#%EF%B8%8F-only-css-and-postcss-are-validated-by-default) for information on how to use > different syntaxes.

⚠️ Stylelint is No Longer Bundled

Unlike 0.x, 1.x no longer provides a copy of Stylelint bundled with the extension. > Bundling Stylelint brought up many unwanted side effects and significantly increased the > extension's size.

Starting with 1.x, vscode-stylelint will depend on having a copy of Stylelint installed > in the open workspace (recommended) or globally (not recommended). If the extension > doesn't seem to be linting any documents, make sure you have Stylelint installed.

⚠️ Only CSS and PostCSS are Validated by Default

The 0.x versions of this extension, which used Stylelint 13.x and prior, supported > validating many different languages out of the box without any additional configuration. > However, this added a lot of complexity and resulted in many cases of unwanted or > unexpected behaviour.

In current versions of the extension, the extension only supports validating CSS and > PostCSS out of the box and requires additional configuration to validate other languages. > You will need to:

  1. Install the PostCSS syntax for the language you want to validate into your workspace, > e.g. [postcss-scss].

  2. Configure Stylelint to use the syntax by providing the module name in the [> customSyntax] option using overrides (or use the [corresponding option]> (#stylelintcustomsyntax) in this extension's settings).

    Example Stylelint config:

    module.exports = {
      overrides: [
        {
          files: ["**/*.scss"],
          customSyntax: "postcss-scss"
        }
      ]
    };
  3. Add the [language identifiers] for the documents you want to validate to the > extension's workspace or user settings using the stylelint.validate option.

    Example VS Code config:

    {
      "stylelint.validate": ["css", "scss"]
    }

Extension Settings

Though relying on a Stylelint configuration file in your project is highly recommended, > you can instead use the following [extension settings][vscode settings]:

stylelint.enable

Type: boolean
Default: true

Controls whether this extension is enabled or not.

stylelint.config

Type: Object
Default: null

Sets the Stylelint [config] option. Note that when this option is enabled, Stylelint > doesn't load configuration files.

stylelint.configFile

Type: string
Default: ""

Sets the Stylelint [configFile] option. Path to a JSON, YAML, or JS file that contains > your configuration object. Use this option if you don't want Stylelint to search for a > configuration file.

stylelint.configBasedir

Type: string
Default: ""

Sets the Stylelint [configBasedir] option. The path to the directory to which relative > paths defining "extends" and "plugins" are relative. Only necessary if these values are > relative paths.

stylelint.customSyntax

Type: string
Default: ""

Sets the Stylelint [customSyntax] option, which points to a [PostCSS syntax] module. > Must be either the package name or an absolute path to the module.

e.g.

  "stylelint.customSyntax": "sugarss"

You can use ${workspaceFolder} to refer to the folder opened in VS Code.

e.g.

  "stylelint.customSyntax": "${workspaceFolder}/custom-syntax.js"

stylelint.reportDescriptionlessDisables

Type: boolean
Default: false

Sets the Stylelint [reportDescriptionlessDisables] option. If true, Stylelint reports > stylelint-disable comments without a description.

stylelint.ignoreDisables

Type: boolean
Default: false

Sets the Stylelint [ignoreDisables] option. If true, Stylelint ignores > stylelint-disable (e.g. /* stylelint-disable block-no-empty */) comments.

stylelint.reportNeedlessDisables

Type: boolean
Default: false

Sets the Stylelint [reportNeedlessDisables] option. If true, Stylelint reports errors > for stylelint-disable comments that are not blocking a lint warning.

stylelint.reportInvalidScopeDisables

Type: boolean
Default: false

Sets the Stylelint [reportInvalidScopeDisables] option. If true, Stylelint reports > errors for stylelint-disable comments referring to rules that don't exist within the > configuration object.

stylelint.validate

Type: string[]
Default: ["css", "postcss"]

An array of language identifiers specifying which files to validate.

stylelint.stylelintPath

Type: string
Default: ""

Used to supply a custom path to the Stylelint module.

stylelint.packageManager

Type: "npm" | "yarn" | "pnpm"
Default: "npm"

Controls the package manager to be used to resolve the Stylelint library. This setting > only has an effect if the Stylelint library is resolved globally. Valid values are "npm"> or "yarn" or "pnpm".

stylelint.snippet

Type: string[]
Default: ["css", "postcss"]

An array of language identifiers specifying which files to enable snippets for.

editor.codeActionsOnSave

This extension provides an action that you can use with VS Code's [> editor.codeActionsOnSave][vscode settings] setting. If provided a > source.fixAll.stylelint property set to explicit, all auto-fixable Stylelint errors > will be fixed on save.

  "editor.codeActionsOnSave": {
    "source.fixAll.stylelint": "explicit"
  }

The following turns on auto fix for all providers, not just Stylelint:

  "editor.codeActionsOnSave": {
    "source.fixAll": "explicit"
  }

You can also selectively disable Stylelint:

  "editor.codeActionsOnSave": {
    "source.fixAll": "explicit",
    "source.fixAll.stylelint": "never"
  }

You can also selectively enable and disable specific languages using VS Code's > language-scoped settings. For example, to disable codeActionsOnSave for HTML files, use > the following:

  "[html]": {
    "editor.codeActionsOnSave": {
      "source.fixAll.stylelint": "never"
    }
  }

Commands

This extension contributes the following commands to the command palette:

  • Fix all auto-fixable problems: applies Stylelint resolutions to all automatically > fixable problems.

Troubleshooting

vscode-stylelint writes logs to the VS Code output panel:

![Screenshot of the Output window]> (https://user-images.githubusercontent.com/9868643/139115502-ff3daa37-1793-47da-9ef9-70c57> 06f018a.png)

You can enable more verbose log output by running VS Code with the NODE_ENV environment > variable set to development. You can do this on macOS and *nix by running:

NODE_ENV=development code

And on Windows by running:

cmd /C "set NODE_ENV=development&&code"

Contributors

Stylelint is maintained by volunteers. Without the code contributions from all these > fantastic people, > Stylelint would not exist. [Become a contributor]> (https://github.com/stylelint/vscode-stylelint/contribute).

Sponsors

type="image/svg+xml">

Thank you to all our sponsors! Become a sponsor.

Backers

<object data=> "https://opencollective.com/stylelint/backers.svg?width=420&avatarHeight=48&button=false" > type="image/svg+xml"> <img src=> "https://opencollective.com/stylelint/backers.svg?width=840&avatarHeight=48&button=false> " />

Thank you to all our backers! Become a backer.

Licence

MIT

[postcss extension]: > https://marketplace.visualstudio.com/items?itemName=mhmadhamster.postcss-language [postcss syntax]: https://github.com/postcss/postcss#syntaxes [postcss-scss]: https://www.npmjs.com/package/postcss-scss

[stylelint 14 migration guide]: > https://github.com/stylelint/stylelint/blob/main/docs/migration-guide/to-14.md [customsyntax]: https://stylelint.io/user-guide/usage/options/#customsyntax [config]: https://stylelint.io/user-guide/usage/node-api#config [configfile]: https://stylelint.io/user-guide/usage/options#configfile [configbasedir]: https://stylelint.io/user-guide/usage/options#configbasedir [reportdescriptionlessdisables]: > https://stylelint.io/user-guide/usage/options#reportdescriptionlessdisables [ignoredisables]: https://stylelint.io/user-guide/usage/options#ignoredisables [reportneedlessdisables]: > https://stylelint.io/user-guide/usage/options#reportneedlessdisables [reportinvalidscopedisables]: > https://stylelint.io/user-guide/usage/options#reportInvalidScopeDisables

[command palette]: > https://code.visualstudio.com/docs/getstarted/userinterface#_command-palette [extension installation guide]: > https://code.visualstudio.com/docs/editor/extension-gallery [language identifiers]: > https://code.visualstudio.com/docs/languages/overview#_language-identifier [vs code's built-in linters]: > https://code.visualstudio.com/docs/languages/css#_syntax-verification-linting [vscode settings]: https://code.visualstudio.com/docs/getstarted/settings