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

@startingpoint/stylint-webpack-plugin

v0.2.6

Published

Webpack loader plugin for stylint(linter of stylus files)

Downloads

4

Readme

@startingpoint/stylint-webpack-plugin

Webpack loader plugin for stylint (linter of stylus files)

Install

Install the stylint

npm i stylint -D

Install @startingpoint/stylint-webpack-plugin package

npm i @startingpoint/stylint-webpack-plugin -D

or

yarn add --dev @startingpoint/stylint-webpack-plugin

If you want to use a custom reporter for a stylint, you also need to install it. For example:

npm i stylint-stylish -D

This webpack plugin for stylint, which supports specifying a directory or several directories of your project with a stylus files. Those files will pass through the linter stylint. By default, lint will use the .stylintrc file in the project root if present. But you can configure it in the options. This plugin supports .styl and .vue files.

Usage

In webpack config:

const StylintWebpackPlugin = require('@startingpoint/stylint-webpack-plugin');

plugins: [
    new StylintWebpackPlugin({
        files: './app/blocks',
        reporter: 'stylint-stylish',
        reporterOptions: {verbose: true}
    })
]

In nuxt config:

const StylintWebpackPlugin = require('@startingpoint/stylint-webpack-plugin');
export default {
    ...,

    build: {
        extend (config, ctx) {
            if (ctx.isDev && ctx.isClient) {
                config.plugins.push(new StylintWebpackPlugin({
                    files: ['./pages', './assets'],
                }));
            }
        },
    },

    ...,
}

Options

|Name |Type |Default |Description | |:-------------------:|:--------------:|:--------------:|:-------------------------------------------------------------- | |files |[String,Array]|./ |Stylus files directory or several directories, who need to check| |config |[String] |undefined |Pass in path to custom rules configuration file as a string. If no configuration is passed in, it will use the .stylintrc file in the project root if present. If that file is not present, it will use default stylint rules.| |rules |[Object] |undefined |Pass in an object with rules for stylint to lint by. This will override all default rules| |exclude |[RegExp] |/node_modules/|Regex for ignores files or sub-directories matching pattern| |reporter |[String] |undefined |If you want to use a custom reporter, you can pass in either a string with it's name| |reporterOptions|[Object] |undefined |Options for your custom reporter|