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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@outcome-co/eslint-plugin-vue-classifier

v1.0.0

Published

An Eslint helper to apply different rules to TS vs JS Vue SFCs.

Readme

eslint-plugin-vue-classifier-js

Release version-badge

An eslint plugin that provides a processor to extract the script type from Vue SFC files.

This allows you to apply different linting rules to the <script> part of your SFCs, based on the lang attribute (e.g. <script lang="ts">).

Installation

npm install @outcome-co/eslint-plugin-vue-classifier

Usage

Inside your eslint config, you should add something similar to the following:

{
    overrides: [
        {
            // For .vue files, use the standard vue-eslint-parser
            // with the vue-classifier plugin
            // The vue-classifier plugin contains a preprocessor that will emit a
            // code block with the extension that corresponds to the script type
            files: ['**/*.vue'],
            plugins: ['@outcome-co/vue-classifier'],
            parser: 'vue-eslint-parser',
            parserOptions: {
                // You can leave typescript here, as it handles both JS and TS
                parser: '@typescript-eslint/parser'
            }
        },
        {
            // The *.vue/*.ts pattern matches the TS code blocks emitted from .vue files 
            files: ['**/*.vue/*.ts'],
            parser: 'vue-eslint-parser',
            parserOptions: {
                parser: '@typescript-eslint/parser',
                // It's important to set createDefaultProgram to true, as we're compiling fragments
                // that the typescript compiler can't find on it's own
                createDefaultProgram: true
            },
            rules: {
                // Some typescript rules...
            }
        },
        {
            // The *.vue/*.fs pattern matches the JS code blocks emitted from .vue files 
            files: ['**/*.vue/*.js'],
            parser: 'vue-eslint-parser',
            parserOptions: {
                parser: '@typescript-eslint/parser',
                // It's important to set createDefaultProgram to true, as we're compiling fragments
                // that the typescript compiler can't find on it's own
                createDefaultProgram: true
            },
            rules: {
                // Some JS rules...
            }
        }
    ]
}

Development

Remember to run ./pre-commit.sh when you clone the repository.