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

validate-html-links-webpack-plugin

v1.0.0

Published

A plugin for webpack which replaces invalid links in HTML files.

Downloads

8

Readme

Installation

npm install validate-html-links-webpack-plugin --save-dev

Usage

The plugin replaces invalid names of resource links with correct names relative to project path. This is especially useful when files contains chunkhash and there is no other way to change this at compile time.

const ValidateHTMLLinksPlugin = require('validate-html-links-webpack-plugin');

module.exports = {
    plugins: [
        new ValidateHTMLLinksPlugin()
    ]
}

Options

| Name | Type | Default | Description | | :---------: |:---------------:| :------------------------:|:------------| | types | Array<String> | ['html', 'css', 'js'] | The types for validation and replacement. Must include html type. | | exclude | Array<String> | [] | The files that will not be processed. If you include html file, then the entire file will be skipped.| | output | Boolean |true | Show in the compilation output what has been changed. |

Example how to set these options:

const ValidateHTMLLinksPlugin = require('validate-html-links-webpack-plugin');

module.exports = {
    plugins: [
        new ValidateHTMLLinksPlugin({
            types: ['html', 'js'],
            exclude: ['/interface/js/scripts/popup.js'],
            output: false
        })
    ]
}

Validation Examples

Be aware that links compares by (a-z | A-Z | 0-9 | .). If comparable link has the same path and difference only in the ([[:alnum:]]|\.), then it will be the same link.

In short, match conditions:

  • same path;
  • difference of name only in range of a-z, A-Z, 0-9 or '.';
  • same type.
/interface/js/scripts/popup.js === /interface/js/scripts/popup.abc123.min.js
/interface/js/scripts/popup.js === /interface/js/scripts/popup.another.js // be careful with dot names!
/interface/js/scripts/popup.js !== /interface/js/scripts/popup-another.js
/interface/js/scripts/popup.js !== /interface/js/scripts/popup-another.abc123.min.js
/interface/js/popup.js !== /interface/js/scripts/popup.js
/interface/js/scripts/popup.js !== /interface/js/scripts/popup.css

Issues and requests

Feel free to use issues. Pull requests are also always welcome!