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

grunt-vnuserver-dev

v2.0.0

Published

A Grunt plugin for starting the vnu.jar markup checker in server mode.

Downloads

26

Readme

grunt-vnuserver-dev

Dependency Status devDependency Status

Grunt plugin for starting the vnu.jar markup checker in server mode. Plays well with grunt-html-dev for faster HTML validation by only starting vnu.jar once, as startup can take a few seconds.

This fork publishes a new grunt-vnuserver-dev NPM module, which depends on vnu-jar@next instead of the latest release of vnu-jar. The W3C Markup Validation Service uses the development version of vnu-jar too. If you want to get consistent results from on-line and off-line testing, you should use grunt-vnuserver-dev instead of grunt-vnuserver in your project.

Getting Started

Install this grunt plugin next to your project's Gruntfile.js with:

npm install grunt-vnuserver-dev --save-dev

Then add this line to your project's Gruntfile.js:

grunt.loadNpmTasks('grunt-vnuserver-dev');

Options

port

  • Type: Number
  • Default: 8888

The port on which to start the server.

all: {
  options: {
      port: 8877
  },
}

skippable

  • Type: Boolean
  • Default: false

Whether or not to skip server startup if port is already in use. Task will fail if port is in use and skippable and useAvailablePort are false.

persist

  • Type: Boolean
  • Default: false

Whether or not to keep the vnu server running even after grunt exists. If false, vnu server is killed when grunt exists.

useAvailablePort

  • Type: Boolean
  • Default: false

If true the task will look for the next available port, if the port set by the port option is in use.

Example

Consider the following configuration in Gruntfile.js in which the watch task is set to run htmllint every time the source file changes. By starting the validator in server mode once using the vnuserver task, validations by htmllint can be performed much faster by simply connecting to this already-running server.

module.exports = function (grunt) {
    grunt.initConfig({
        vnuserver: {
        },
        htmllint: {
            all: {
                options: {
                    // This option makes grunt-html-dev connect to the vnu server instance.
                    server: {}
                },
                src: "app.html"
            }
        },
        watch: {
            all: {
                tasks: ['htmllint'],
                files: "app.html"
            }
        },
    });

    grunt.loadNpmTasks('grunt-vnuserver-dev');
    grunt.loadNpmTasks('grunt-html-dev');
    grunt.loadNpmTasks('grunt-contrib-watch');

    grunt.registerTask('default', ['vnuserver', 'watch']);
};

Using the First Available Port

If you set useAvailablePort to true, you will need to pass the actual value to the htmllint task, but the value will be known first during the runtime. Use a function for the server option, which was introduced in the grunt-html-dev fork, at first.

module.exports = function (grunt) {
    var vnuPort;

    grunt.initConfig({
        vnuserver: {
            // Name the task to be able to listen to its events.
            options: {
                // Start with the first free ephemeral port.
                port: 49152,
                // Try other ports, up to port + 30, if the first one is not free.
                useAvailablePort: true
            }
        },
        htmllint: {
            options: {
                // Connect to the vnu server on the dynamically chosen  port.
                server: function () {
                    return {
                        port: vnuPort
                    };
                }
            },
            all: {
                src: "app.html"
            }
        },
        watch: {
            all: {
                tasks: ['htmllint'],
                files: "app.html"
            }
        },
    });

    grunt.loadNpmTasks('grunt-vnuserver-dev');
    grunt.loadNpmTasks('grunt-html-dev');
    grunt.loadNpmTasks('grunt-contrib-watch');

    // Obtain the port, which the vnu server is listening to.
    grunt.event.on('vnuserver.listening', function (port) {
        vnuPort = port;
        // vnuPort = grunt.config.get('vnuserver.options.port');
    });

    grunt.registerTask('default', ['vnuserver', 'watch']);
};

License

Copyright Bennie Swart. Licensed under the MIT license.