Vuegister is a require hook for loading of the Vue.js single-file components (or *.vue files).

Overview

vuegister npm version build status

About

Vuegister (a portmanteau for vue-register) is a require hook for loading of the Vue.js single-file components (or *.vue files). The main purpose of this package is to help the developer with unit testing of the component's logic. It allows you to import the object from the *.vue template as you do it with any Node.js module.

Sometimes you want to run multiple small tests simultaneously. Opening a new page with test suite in browser (even in PhantomJS) can take minutes. With the help of jsdom it is possible to speed up this process. You can run your unit tests in the pure Node.js environment. There is no need in heavy test runners (like Karma) or code transpilers (like Babel). Actual versions of Node.js supports new features from the latest revision of the JavaScript ECMA-262 specification. The website node.green provides overview of supported ECMAScript features in various versions of Node.js.

This package doesn't perform any transpiling of the code. Vuegister just extracts text between script tags, adds source map and passes the result to Module.prototype._compile. The module._compile method can only run JavaScript code (not CoffeeScript or Babel dependent). At the same time you can use external plugins for the code transpiling. Please see the Plugins section of this document.

Installation

npm i vuegister -D

Plugins

Vuegister can be easily extended through plugins to support various code preprocessors. Take a look at the babel plugin for further details.

Usage

Register *.vue extension from Node.js:

require('vuegister').register()

Using require hook from the Mocha test framework. This is equivalent to Babel’s babel-register:

mocha --require vuegister/register

Test suite example

To run test suite create test.js and MyComponent.vue files inside your test folder.

Content of the test.js file:

const assert = require('chai').assert;
const Vue = require('vue/dist/vue.common')
const MyComponent = require('./MyComponent.vue')

describe('MyComponent', () => {
  it('has a created hook', () => {
    assert.isFunction(MyComponent.created)
  })

  it('sets the correct default data', () => {
    assert.isFunction(MyComponent.data)
    const defaultData = MyComponent.data()
    assert.strictEqual(defaultData.message, 'hello!')
  })

  it('correctly sets the message when created', () => {
    const vm = new Vue(MyComponent).$mount()
    assert.strictEqual(vm.message, 'bye!')
  })

  it('renders the correct message', () => {
    const Ctor = Vue.extend(MyComponent)
    const vm = new Ctor().$mount()
    assert.strictEqual(vm.$el.textContent, 'bye!')
  })
})

Content of the MyComponent.vue file:

<template>
  <span>{{ message }}span>
template>
<script>
  module.exports = {
    data () {
      return {
        message: 'hello!'
      }
    },
    created () {
      this.message = 'bye!'
    }
  }
script>

Install jsdom-global and run tests with:

npm i jsdom jsdom-global -D
mocha -r jsdom-global/register -r vuegister/register

API Reference

Project documentation is generated automatically from source code. Please take a look at the api.md file in this repository.

Tests

To run the test suite, install development dependencies and execute:

npm run coverage

License

Distributed under MIT License.

Comments
  • Update eslint to the latest version 🚀

    Update eslint to the latest version 🚀

    Version 4.1.0 of eslint just got published.

    Dependency eslint
    Current Version 3.19.0
    Type devDependency

    The version 4.1.0 is not covered by your current version range.

    Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.

    I recommend you look into these changes and try to get onto the latest version of eslint. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.


    Release Notes v4.1.0
    • e8f1362 Docs: Remove wrong descriptions in padded-block rule (#8783) (Plusb Preco)
    • 291a783 Update: enforceForArrowConditionals to no-extra-parens (fixes #6196) (#8439) (Evilebot Tnawi)
    • a21dd32 New: Add overrides/files options for glob-based config (fixes #3611) (#8081) (Sylvan Mably)
    • 879688c Update: Add ignoreComments option to no-trailing-spaces (#8061) (Jake Roussel)
    • b58ae2e Chore: Only instantiate fileEntryCache when cache flage set (perf) (#8763) (Gyandeep Singh)
    • 9851288 Update: fix indent errors on multiline destructure (fixes #8729) (#8756) (Victor Hom)
    • 3608f06 Docs: Increase visibility of code of conduct (fixes #8758) (#8764) (Kai Cataldo)
    • 673a58b Update: support multiple fixes in a report (fixes #7348) (#8101) (Toru Nagashima)
    • 7a1bc38 Fix: don't pass default parserOptions to custom parsers (fixes #8744) (#8745) (Teddy Katz)
    • c5b4052 Chore: enable computed-property-spacing on ESLint codebase (#8760) (Teddy Katz)
    • 3419f64 Docs: describe how to use formatters on the formatter demo page (#8754) (Teddy Katz)
    • a3ff8f2 Chore: combine tests in tests/lib/eslint.js and tests/lib/linter.js (#8746) (Teddy Katz)
    • b7cc1e6 Fix: Space-infix-ops should ignore type annotations in TypeScript (#8341) (Reyad Attiyat)
    • 46e73ee Fix: eslint --init installs wrong dependencies of popular styles (fixes #7338) (#8713) (Toru Nagashima)
    • a82361b Chore: Prevent package-lock.json files from being created (fixes #8742) (#8747) (Teddy Katz)
    • 5f81a68 New: Add eslintIgnore support to package.json (fixes #8458) (#8690) (Victor Hom)
    • b5a70b4 Update: fix multiline binary operator/parentheses indentation (#8719) (Teddy Katz)
    • ab8b016 Update: fix MemberExpression indentation with "off" option (fixes #8721) (#8724) (Teddy Katz)
    • eb5d12c Update: Add Fixer method to Linter API (#8631) (Gyandeep Singh)
    • 26a2daa Chore: Cache fs reads in ignored-paths (fixes #8363) (#8706) (Victor Hom)
    Commits

    The new version differs by 141 commits.

    • 7d9e3be 4.1.0
    • e727b7b Build: changelog update for 4.1.0
    • e8f1362 Docs: Remove wrong descriptions in padded-block rule (#8783)
    • 291a783 Update: enforceForArrowConditionals to no-extra-parens (fixes #6196) (#8439)
    • a21dd32 New: Add overrides/files options for glob-based config (fixes #3611) (#8081)
    • 879688c Update: Add ignoreComments option to no-trailing-spaces (#8061)
    • b58ae2e Chore: Only instantiate fileEntryCache when cache flage set (perf) (#8763)
    • 9851288 Update: fix indent errors on multiline destructure (fixes #8729) (#8756)
    • 3608f06 Docs: Increase visibility of code of conduct (fixes #8758) (#8764)
    • 673a58b Update: support multiple fixes in a report (fixes #7348) (#8101)
    • 7a1bc38 Fix: don't pass default parserOptions to custom parsers (fixes #8744) (#8745)
    • c5b4052 Chore: enable computed-property-spacing on ESLint codebase (#8760)
    • 3419f64 Docs: describe how to use formatters on the formatter demo page (#8754)
    • a3ff8f2 Chore: combine tests in tests/lib/eslint.js and tests/lib/linter.js (#8746)
    • b7cc1e6 Fix: Space-infix-ops should ignore type annotations in TypeScript (#8341)

    There are 141 commits in total.

    See the full diff

    Not sure how things should work exactly?

    There is a collection of frequently asked questions and of course you may always ask my humans.


    Your Greenkeeper Bot :palm_tree:

    greenkeeper 
    opened by greenkeeper[bot] 8
  • Update acorn to the latest version 🚀

    Update acorn to the latest version 🚀

    Version 5.0.0 of acorn just got published.

    Dependency acorn
    Current Version 4.0.12
    Type dependency

    The version 5.0.0 is not covered by your current version range.

    Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.

    I recommend you look into these changes and try to get onto the latest version of acorn. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.


    Commits

    The new version differs by 1 commits .

    See the full diff.

    Not sure how things should work exactly?

    There is a collection of frequently asked questions and of course you may always ask my humans.


    Your Greenkeeper Bot :palm_tree:

    greenkeeper 
    opened by greenkeeper[bot] 3
  • Update eslint-config-google to the latest version 🚀

    Update eslint-config-google to the latest version 🚀

    Version 0.9.0 of eslint-config-google just got published.

    Dependency eslint-config-google
    Current Version 0.8.1
    Type devDependency

    The version 0.9.0 is not covered by your current version range.

    Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.

    I recommend you look into these changes and try to get onto the latest version of eslint-config-google. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.


    Commits

    The new version differs by 2 commits.

    See the full diff

    Not sure how things should work exactly?

    There is a collection of frequently asked questions and of course you may always ask my humans.


    Your Greenkeeper Bot :palm_tree:

    greenkeeper 
    opened by greenkeeper[bot] 1
  • An in-range update of mocha is breaking the build 🚨

    An in-range update of mocha is breaking the build 🚨

    Version 3.4.0 of mocha just got published.

    Branch Build failing 🚨
    Dependency mocha
    Current Version 3.3.0
    Type devDependency

    This version is covered by your current version range and after updating it in your project the build failed.

    As mocha is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

    I recommend you give this issue a high priority. I’m sure you can resolve this :muscle:

    Status Details
    • continuous-integration/travis-ci/push The Travis CI build failed Details

    Release Notes v3.4.0

    Mocha is now moving to a quicker release schedule: when non-breaking changes are merged, a release should happen that week.

    This week's highlights:

    • allowUncaught added to commandline as --allow-uncaught (and bugfixed)
    • warning-related Node flags

    🎉 Enhancements

    🐛 Fixes

    🔩 Other

    Commits

    The new version differs by 9 commits0.

    • 7554b31 Add Changelog for v3.4.0
    • 9f7f7ed Add --trace-warnings flag
    • 92561c8 Add --no-warnings flag
    • ceee976 lint test/integration/fixtures/simple-reporter.js
    • dcfc094 Revert "use semistandard directly"
    • 93392dd no special case for macOS running Karma locally
    • 4d1d91d --allow-uncaught cli option
    • fb1e083 fix allowUncaught in browser
    • 4ed3fc5 Add license report and scan status

    false

    See the full diff

    Not sure how things should work exactly?

    There is a collection of frequently asked questions and of course you may always ask my humans.


    Your Greenkeeper Bot :palm_tree:

    greenkeeper 
    opened by greenkeeper[bot] 1
  • nested template issue

    nested template issue

    Hi!

    I find some issue with nested <template> tags. I'm use your vuegister with jest as vue SFC transpiler htmlParser2 within extract method returns list of this tags and break vue-test-utils render function

    opened by shifteee 0
  • An in-range update of chai is breaking the build 🚨

    An in-range update of chai is breaking the build 🚨

    Version 4.0.2 of chai just got published.

    Branch Build failing 🚨
    Dependency chai
    Current Version 4.0.1
    Type devDependency

    This version is covered by your current version range and after updating it in your project the build failed.

    As chai is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

    I recommend you give this issue a high priority. I’m sure you can resolve this :muscle:

    Status Details
    • continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

    Release Notes 4.0.2 / 2017-06-05

    We have another bugfix release, addressing some issues for WebPack 1 users.

    Bug Fixes

    • Revert getting version information from package.json, some bundler tools like Webpack do not come default with json loaders despite Node being able to handle this. This change moves back to hardcoding the version number in the codebase. (#985, #986)
    Commits

    The new version differs by 1 commits.

    • 616cf8b Revert get version package json (#986)

    See the full diff

    Not sure how things should work exactly?

    There is a collection of frequently asked questions and of course you may always ask my humans.


    Your Greenkeeper Bot :palm_tree:

    greenkeeper 
    opened by greenkeeper[bot] 0
  • Update eslint-config-google to the latest version 🚀

    Update eslint-config-google to the latest version 🚀

    Version 0.8.0 of eslint-config-google just got published.

    Dependency eslint-config-google
    Current Version 0.7.1
    Type devDependency

    The version 0.8.0 is not covered by your current version range.

    Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.

    I recommend you look into these changes and try to get onto the latest version of eslint-config-google. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.


    Commits

    The new version differs by 9 commits.

    • 699a43f Release version 0.8.0
    • e24704c Update keyword-spacing rule
    • d7a198d Merge pull request #42 from stramel/patch-2
    • d7073f3 Re-add TODO
    • a26e753 Merge pull request #39 from pragmaticivan/patch-1
    • 0753850 Update curly lint rule
    • a9cd6ed Removes extra space before 'use strict'
    • d13ead7 Merge pull request #32 from fbergr/readme
    • df4c49d Fix link to style guide in readme

    See the full diff

    Not sure how things should work exactly?

    There is a collection of frequently asked questions and of course you may always ask my humans.


    Your Greenkeeper Bot :palm_tree:

    greenkeeper 
    opened by greenkeeper[bot] 0
  • Update nyc to the latest version 🚀

    Update nyc to the latest version 🚀

    Version 11.0.2 of nyc just got published.

    Dependency nyc
    Current Version 10.3.2
    Type devDependency

    The version 11.0.2 is not covered by your current version range.

    Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.

    I recommend you look into these changes and try to get onto the latest version of nyc. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.


    Commits

    The new version differs by 13 commits.

    • e4eff12 chore(release): 11.0.2
    • 0c2ef43 chore: upgrade to newer version of spawn-wrap (#592)
    • 9d47986 chore(release): 11.0.1
    • fa1097a chore: acutally swap in new copy of signals.js
    • 8662357 chore: hack to fix SIGPROF binding issue on node 8
    • d90aed6 chore(release): 11.0.0
    • 2f68559 chore: hack to prevent SIGPROF warning, until new spawn-wrap is available
    • f18f780 fix: add support for ES6 modules
    • 0e6b277 chore: formatting nit
    • 80ef0a3 docs: mention the ability to publish configuration in docs
    • 33829b8 feat: upgrade to version of yargs with support for presets
    • 55b68b5 chore: update istanbuljs dependencies (#583)
    • a1a457f feat: allow .nycrc.json (#580)

    See the full diff

    Not sure how things should work exactly?

    There is a collection of frequently asked questions and of course you may always ask my humans.


    Your Greenkeeper Bot :palm_tree:

    greenkeeper 
    opened by greenkeeper[bot] 0
  • Update jsdoc-to-markdown to the latest version 🚀

    Update jsdoc-to-markdown to the latest version 🚀

    Version 3.0.0 of jsdoc-to-markdown just got published.

    Dependency jsdoc-to-markdown
    Current Version 2.0.1
    Type devDependency

    The version 3.0.0 is not covered by your current version range.

    Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.

    I recommend you look into these changes and try to get onto the latest version of jsdoc-to-markdown. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.


    Commits

    The new version differs by 9 commits .

    • e31891d 3.0.0
    • 99b01bc 3.0.0-0
    • e881561 upgrade deps
    • 80dcf1b fix test on node 4
    • a7dd63c remove support for node < v4.0.0
    • eb3927b use core-assert for node v0.12.0 compatibility
    • 177641b upgrade deps.. additional test
    • ab30db1 add node v7 to travis, remove v0.10
    • 26629f2 docs: fix errors in render() and renderSync() examples

    See the full diff.

    Not sure how things should work exactly?

    There is a collection of frequently asked questions and of course you may always ask my humans.


    Your Greenkeeper Bot :palm_tree:

    greenkeeper 
    opened by greenkeeper[bot] 0
  • Create .codeclimate.yml with eslint-2 channel

    Create .codeclimate.yml with eslint-2 channel

    Before merging this, install a webhook for Code Climate so it can see subsequent commits:

    Then, merge this inferred .codeclimate.yml with "eslint-2" channel.

    opened by efueger 0
  • Add Greenkeeper badge 🌴

    Add Greenkeeper badge 🌴

    Let’s get started with automated dependency management for vuegister :muscle:

    All your dependencies are up-to-date right now, so this repository was enabled right away. Good job :thumbsup:

    There is a badge added to your README, indicating the status of this repository. This is what it looks like :point_right: Greenkeeper badge


    🙈 How to ignore certain dependencies

    In case you can not, or do not want to update a certain dependency right now, you can of course just change the package.json file back to your liking.

    Add a greenkeeper.ignore field to your package.json, containing a list of dependencies you don’t want to update right now.

    // package.json
    {
      …
      "greenkeeper": {
        "ignore": [
          "package-names",
          "you-want-me-to-ignore"
        ]
      }
    }
    
    ✨ How the updates will look like

    As soon as you merge this pull request I’ll create a branch for every dependency update, with the new version applied. The branch creation should trigger your testing services to check the new version. Using the results of these tests I’ll try to open meaningful and helpful pull requests and issues, so your dependencies remain working and up-to-date.

    -  "underscore": "^1.6.0"
    +  "underscore": "^1.7.0"
    

    In the above example you can see an in-range update. 1.7.0 is included in the old ^1.6.0 range, because of the caret ^ character. When the test services report success I’ll delete the branch again, because no action needs to be taken – everything is fine. When there is a failure however, I’ll create an issue so you know about the problem immediately.

    This way every single version update of your dependencies will either continue to work with your project, or you’ll get to know of potential problems immediately.

    -  "lodash": "^3.0.0"
    +  "lodash": "^4.0.0"
    

    In this example the new version 4.0.0 is not included in the old ^3.0.0 range. For version updates like these – let’s call them “out of range” updates – you’ll receive a pull request.

    Now you no longer need to check for exciting new versions by hand – I’ll just let you know automatically. And the pull request will not only serve as a reminder to update. In case it passes your decent test suite that’s a strong reason to merge right away :shipit:

    💁‍♂️ Not sure how things are going to work exactly?

    There is a collection of frequently asked questions and of course you may always ask my humans.


    Good luck with your project and see you soon :sparkles:

    Your Greenkeeper Bot :palm_tree:

    greenkeeper 
    opened by greenkeeper[bot] 0
  • Update htmlparser2 to the latest version 🚀

    Update htmlparser2 to the latest version 🚀

    The dependency htmlparser2 was updated from 3.10.1 to 4.0.0.

    This version is not covered by your current version range.

    If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.


    Publisher: feedic License: MIT

    Find out more about this release.


    FAQ and help

    There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


    Your Greenkeeper bot :palm_tree:

    greenkeeper 
    opened by greenkeeper[bot] 0
  • An in-range update of htmlparser2 is breaking the build 🚨

    An in-range update of htmlparser2 is breaking the build 🚨

    The dependency htmlparser2 was updated from 3.9.2 to 3.10.0.

    🚨 View failing branch.

    This version is covered by your current version range and after updating it in your project the build failed.

    htmlparser2 is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

    Status Details
    • continuous-integration/travis-ci/push: The Travis CI build failed (Details).

    Commits

    The new version differs by 12 commits.

    • a0002c2 3.10.0
    • 8e132d0 ignore node_modules dir
    • 76895d5 Correctly handle SVG (and MathML) tag closing (#254)
    • 0f72363 fix(package): update readable-stream to version 3.0.6 (#249)
    • d7d2a33 chore(package): update mocha to version 5.2.0 (#234)
    • 11e4441 Fix premature cdata end detection with conditional comments (#235)
    • 297827f Remove require for stream (#233)
    • 1732d7e Enable Greenkeeper
    • 27c55b2 Update deps (#232)
    • a706ab0 Set theme jekyll-theme-cayman
    • da78791 readme: Change live demo to AST explorer
    • 42fa5b3 travis: Update node versions (#196)

    See the full diff

    FAQ and help

    There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


    Your Greenkeeper Bot :palm_tree:

    greenkeeper 
    opened by greenkeeper[bot] 1
  • Update acorn to the latest version 🚀

    Update acorn to the latest version 🚀

    The dependency acorn was updated from 5.7.3 to 6.0.0.

    This version is not covered by your current version range.

    If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.


    Find out more about this release.

    FAQ and help

    There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


    Your Greenkeeper bot :palm_tree:

    greenkeeper 
    opened by greenkeeper[bot] 13
  • Update eslint-config-google to the latest version 🚀

    Update eslint-config-google to the latest version 🚀

    Version 0.10.0 of eslint-config-google was just published.

    Dependency eslint-config-google
    Current Version 0.8.1
    Type devDependency

    The version 0.10.0 is not covered by your current version range.

    If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.

    It might be worth looking into these changes and trying to get this project onto the latest version of eslint-config-google.

    If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.


    Commits

    The new version differs by 10 commits.

    • 766265c Release version 0.10.0
    • c2d3673 Merge pull request #50 from mathiasbynens/indent
    • 1fdcfc2 Indent continuation lines at least 4 spaces
    • 394bf3c Merge pull request #46 from posquit0/patch-1
    • 8d4af1d Fix mis-typing
    • 968e335 Release version 0.9.1
    • f600349 Add package-lock.json
    • 5626690 Fix test failures
    • b244e6e Release version 0.9.0
    • 8da7124 Update rules to eslint 4.1.1

    See the full diff

    FAQ and help

    There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


    Your Greenkeeper bot :palm_tree:

    greenkeeper 
    opened by greenkeeper[bot] 3
  • Update eslint to the latest version 🚀

    Update eslint to the latest version 🚀

    Version 5.0.0 of eslint was just published.

    Dependency [eslint](https://github.com/eslint/eslint)
    Current Version 4.19.1
    Type devDependency

    The version 5.0.0 is not covered by your current version range.

    If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.

    It might be worth looking into these changes and trying to get this project onto the latest version of eslint.

    If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.


    Release Notes v5.0.0

    Release blogpost

    Migration guide

    • 0feedfd New: Added max-lines-per-function rule (fixes #9842) (#10188) (peteward44)
    • daefbdb Upgrade: eslint-scope and espree to 4.0.0 (refs #10458) (#10500) (Brandon Mills)
    • 077358b Docs: no-process-exit: recommend process.exitCode (#10478) (Andres Kalle)
    • f93d6ff Fix: do not fail on unknown operators from custom parsers (fixes #10475) (#10476) (Rubén Norte)
    • 05343fd Fix: add parens for yield statement (fixes #10432) (#10468) (Pig Fang)
    • d477c5e Fix: check destructuring for "no-shadow-restricted-names" (fixes #10467) (#10470) (Pig Fang)
    • 7a7580b Update: Add considerPropertyDescriptor option to func-name-matching (#9078) (Dieter Luypaert)
    • e0a0418 Fix: crash on optional catch binding (#10429) (Toru Nagashima)
    • de4dba9 Docs: styling team members (#10460) (薛定谔的猫)
    • 5e453a3 Docs: display team members in tables. (#10433) (薛定谔的猫)
    • b1895eb Docs: Restore intentional spelling mistake (#10459) (Wilfred Hughes)
    Commits

    The new version differs by 148 commits.

    • 36ced0a 5.0.0
    • 5fd5632 Build: changelog update for 5.0.0
    • 0feedfd New: Added max-lines-per-function rule (fixes #9842) (#10188)
    • daefbdb Upgrade: eslint-scope and espree to 4.0.0 (refs #10458) (#10500)
    • 077358b Docs: no-process-exit: recommend process.exitCode (#10478)
    • f93d6ff Fix: do not fail on unknown operators from custom parsers (fixes #10475) (#10476)
    • 05343fd Fix: add parens for yield statement (fixes #10432) (#10468)
    • d477c5e Fix: check destructuring for "no-shadow-restricted-names" (fixes #10467) (#10470)
    • 7a7580b Update: Add considerPropertyDescriptor option to func-name-matching (#9078)
    • e0a0418 Fix: crash on optional catch binding (#10429)
    • de4dba9 Docs: styling team members (#10460)
    • 5e453a3 Docs: display team members in tables. (#10433)
    • b1895eb Docs: Restore intentional spelling mistake (#10459)
    • a9da57d 5.0.0-rc.0
    • 3ac3df6 Build: changelog update for 5.0.0-rc.0

    There are 148 commits in total.

    See the full diff

    FAQ and help

    There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


    Your Greenkeeper bot :palm_tree:

    greenkeeper 
    opened by greenkeeper[bot] 17
  • Update nyc to the latest version 🚀

    Update nyc to the latest version 🚀

    Version 12.0.1 of nyc was just published.

    Dependency nyc
    Current Version 11.9.0
    Type devDependency

    The version 12.0.1 is not covered by your current version range.

    If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.

    It might be worth looking into these changes and trying to get this project onto the latest version of nyc.

    If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don’t have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.


    Commits

    The new version differs by 4 commits.

    • 9fc20e4 chore(release): 12.0.1
    • 3e087d4 chore: upgrade to version of istanbul with optional catch binding (#851)
    • eaf3f70 chore(release): 12.0.0
    • 19b7d21 chore: upgrade to newest version of istanbul codebase (#848)

    See the full diff

    FAQ and help

    There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


    Your Greenkeeper bot :palm_tree:

    greenkeeper 
    opened by greenkeeper[bot] 6
Owner
Aleksei Iatsiuk
Aleksei Iatsiuk
A Webpack loader which extracts a single block from Vue single-file components

vue-extraxt-loader A Webpack loader which extracts a single block from Vue single-file components. What is the difference with vue-loader? Beside impo

Nicolò Ribaudo 5 Sep 27, 2019
webpack loader, loads the .md file and returns the webpack loader that contains the content string in the file to achieve the function of making webpack load the .md file

webpack loader, loads the .md file and returns the webpack loader that contains the content string in the file to achieve the function of making webpack load the .md file

socialuni 0 Dec 28, 2020
Vue-loading - Vue Placeholder loading Content With Image,Table,Status

Vue Loading Project setup npm install Compiles and hot-reloads for development

Vũ Đức Việt 3 Jan 30, 2022
A text loading component for Vue.js. Uses SVG and javascript to animate a text loading with a gradient.

A text loading component for Vue.js. Uses SVG and javascript to animate a text loading with a gradient.

null 1 Aug 3, 2020
SVG component to create placeholder loading, like Facebook cards loading.

SVG component to create placeholder loading, like Facebook cards loading.

EGOIST 2.9k Sep 29, 2022
Data loading animation component for VueJS, inspired by video games loading screens.

Data loading animation component for VueJS, inspired by video games loading screens.

null 0 Sep 1, 2020
Webpack loader to be used along with vue-loader for Single File Components that provides template extension

vue-inheritance-loader Webpack loader to be used along with vue-loader for Single File Components that provides template extension. In Vue its possibl

Matias Rodal 39 May 24, 2021
💥Browser Vue Loader is a single file JavaScript library that loads untranspile Vue applications into the browsers.

Browser Vue Loader Browser Vue Loader is a single file JavaScript library that loads untranspile Vue applications into the browsers. This loader is id

Xinzi Zhou 28 Jul 13, 2022
Vue3/Vue2 Single File Component loader

Single File Component loader for Vue2 and Vue3. Load .vue files directly from your HTML. No node.js environment, no build step.

Franck Freiburger 527 Sep 26, 2022
💫 A collection of loading spinner components for Vuejs

Vue Spinners A Vue.js port of react-spinners. ?? Installation npm install --save @saeris/vue-spinners # or yarn add @saeris/vue-spinners ?? Usage Ther

Drake Costa 308 Sep 26, 2022
md-vue-loader is a Webpack loader to import Markdown files as Vue components

md-vue-loader md-vue-loader is a Webpack loader to import Markdown files as Vue components. ?? Why? ?? Decoupled from Vue Compatible with any version

hiroki osame 4 Jan 11, 2022
Vite 2.x plugin to load SVG files as Vue components

Vite SVG loader Vite 2.x plugin to load SVG files as Vue components. <template> <MyIcon /> </template> <script setup> import MyIcon from './my-icon

Jan-Paul Kleemans 237 Sep 27, 2022
Vue-simple-loading: Fork styles from tobiasahlin/SpinKit and built it for vue

vue-simple-loading Thanks for tobiasahlin/SpinKit. The css3 animation is copied from it. All the things I do is built it as a vue component. This proj

Heath Yang 14 Dec 17, 2020
Progress bars and loading indicators for Vue.js

vue-progress-path Progress bars and loading indicators that can take any form! This library is Work In Progress. Live Demo Sponsors Gold Silver Bronze

Guillaume Chau 403 Sep 20, 2022
BlockUI for vue 2, similiar to jquery blockUI, can be used for loading screen.

vue-blockui BlockUI for vue 2, similiar to jquery blockUI, can be used for loading screen. Table of contents Installation Usage Demo Screens Installat

Jeff 57 Apr 6, 2022
Vue.js component for full screen loading indicator :cyclone:

Vue Loading Overlay Component Vue.js component for full screen loading indicator Demo or JSFiddle Installation # yarn yarn add vue-loading-overlay #

Ankur Kumar 1.1k Sep 27, 2022
⏳ Loading inside a container or full screen for Vue.js

vue-element-loading ⏳ Loading inside a container or full screen for Vue.js ?? Document & Demo Page Docs & Live demo Fully feature live demo ?? Install

Pongsatorn 312 Sep 4, 2022
a vue component about toy bricks of skeleton screen loading

tb-skeleton a vue component about toy bricks of skeleton screen loading install $ npm i tb-skeleton -s use npm import Vue from 'vue' import skelet

zhoulin 88 Aug 12, 2022
👇 Vue button with slideout loading indicator

vue-loading-button Straightforward Vue button with slideout loading indicator Props Prop Type Required Default Description loading boolean false false

William Lindvall 39 Jun 29, 2022