Motivation

In README.md are added pug-plugin and modern powerful pug-loader.

pug-plugin

This plugin enable to define Pug files in Webpack entry, extracts JS and CSS from sources specified directly in Pug:

const PugPlugin = require('pug-plugin');
module.exports = {
  entry: {
    index: './src/views/index.pug',      // output index.html
    about: './src/views/about/index.pug' // output about.html
    // ..
  },
  plugins: [
    new PugPlugin(/* options */), // enable using Pug files in webpack entry
  ],
};

All source scripts and styles can be required in Pug, e.g.:

link(href=require('./styles.scss') rel='stylesheet')
script(src=require('./main.js'))

Generated HTML contains hashed CSS and JS output filenames:

<link href="/assets/css/styles.05e4dd86.css" rel="stylesheet">
<script src="/assets/js/main.f4b855d8.js"></script>

This plugin make much easy the usage Pug with Webpack.
Test coverage > 99%.

@webdiscus/pug-loader

The original pugjs/pug-loader has problems:

• since 4 years not updated Is this package still being maintained?
• by install occurs deprecation ERROR and can be installed only with force npm i pug-loader --force

The alternative @webdiscus/pug-loader can do absolutely everything that pugjs/pug-loader can (100% compatible with pugjs/pug-loader), plus:

• compiles Pug to template function (as pugjs/pug-loader), but in CommonJS or ESM
• renders Pug to JS module with exports as HTML string, useful for use in JS
• renders Pug to pure HTML string, useful for use with Vue, React, Angular
• pass custom data in Pug templates
• supports for indent in templates of Vue, React:

  <template lang='pug'>
    h1 Hello Pug!
    p Use the '@webdiscus/pug-loader'
  </template>

• resolves all required resoures
• watching of changes in all dependencies
• test coverage > 98%

Suggestion

Instead of install size display publish size of a package.
E.g. the pug-plugin have public size only 100 KB, but install size is 8 MB, becase contains docs with many resources, has much tests with real files to test: images, fonts, etc.

What kind of change does this PR introduce?
docs: update readme

Did you add tests for your changes?
tests are not needs for readme

Does this PR introduce a breaking change?
No

What needs to be documented once your changes are merged?
Nothing