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

@crishellco/vue-coy

v1.4.0

Published

A CLI tool to help identify missing Vue component tests.

Downloads

12

Readme

Vue Coy

A CLI tool to help identify missing Vue component tests.

Table of contents

Install

# in a project
yarn add -D @crishellco/vue-coy

# globally 
yarn global add @crishellco/vue-coy

Usage

What does it look for?

exports.GROUPS_TO_TEST = ['watch', 'computed', 'methods'];
exports.HOOKS_TO_TEST = [
  'beforeCreate',
  'created',
  'beforeMount',
  'mounted',
  'beforeUpdate',
  'updated',
  'activated',
  'deactivated',
  'beforeUnmount',
  'unmounted',
  'beforeDestroy',
  'destroyed',
  'renderTracked',
  'renderTriggered',
  'errorCaptured',
];

When should you use it?

  • in your test suite
  • in your pre-commit hooks
  • in your builds
  • manually as a sanity check

Config (optional)

// coy.config.json
{
  "ignore": ["node_modules"],
  "paths": ["**"], 
  "regex": "(.+)?{key}(.+)?", 
  "testFileExtension": "spec.js" 
}

Options

| Name | Type | Default | Description | |---------------------|----------|--------------------------|-----------------------------------------------------------------------------------------------------| | ignore | Array | ['**/node_modules/**'] | Which folders to ignore (globs) | | paths | Array | ['**'] | Where to look for Vue files (globs) | | regex | String | '(.*?{key}.*?)' | How to determine if a test exists (regex). {key} gets replaced with the name of the missing item. | | testFileExtension | String | 'spec.js' | Test file extension |

Command Line

# in a project
$ yarn coy 
$ yarn coy -c 
$ yarn coy -c master
$ yarn coy -s
$ yarn coy -s path/to/save/report.json
$ yarn coy -w

# globally 
$ coy 
$ coy -c
$ coy -c master
$ coy -s
$ coy -s path/to/save/report.json
$ coy -w

Options

| Flag | Argument | Default | Description | |-----------------|---------------------|----------------------------|------------------------------------------------| | -c, --changed | branch (optional) | master | Only analyze changes compared to a branch | | -s, --save | file (optional) | missing-test-report.json | Saves missing test report to a JSON file | | -w, --watch | | | Watch for changes and reevaluate missing tests | | -h, --help | | | Display help for command |

Display In Terminal (default)

image

Save To File (with -s)

{
  "test/fixtures/missing.vue": {
    "missing": {
      "methods": [
        {
          "key": "foo",
          "link": "test/fixtures/missing.vue:10"
        }
      ]
    },
    "testFile": "test/fixtures/missing.spec.js",
    "testSource": "describe('index.vue', () => {\n  describe('methods', () => {});\n});\n"
  },
  "test/fixtures/no-test.vue": {
    "missing": {
      "methods": [
        {
          "key": "foo",
          "link": "test/fixtures/no-test.vue:10"
        }
      ]
    },
    "testFile": "test/fixtures/no-test.spec.js",
    "testSource": null
  }
}

Ignoring Code

<script>
  export default {
    methods: {
      // coy-ignore-next
      foo() {}
    }
  }
</script>

How to Contribute

Pull Requests

  1. Fork the repository
  2. Create a new branch for each feature or improvement
  3. Please follow semantic-release commit format
  4. Send a pull request from each feature branch to the develop branch

License

MIT