Bump pug-plugin from 2.7.7 to 4.1.0

[dependabot[bot]]

Bumps pug-plugin from 2.7.7 to 4.1.0.

Release notes

Sourced from pug-plugin's releases.

v4.0.0

⚠ BREAKING CHANGES

• Default value PugPlugin.loader.option.method is now render instead of compile, because it makes sense in the vast majority of use cases.
  By compatibility issues (when the method was not specified), add the method option:

{
  loader: PugPlugin.loader,
  options: {
    method: 'compile', // now the default method is `render`
  }
},

• The outputFile property of the ResourceInfo (the argument of postprocess function) was replaced with outputPath.
  By compatibility issues (when in the postprocess was used the outputFile), add in your postprocess function the code line:

new PugPlugin({
  postprocess: (content, info) => {
    const outputFile = path.join(info.outputPath, info.assetFile); // add this line to get the removed outputFile
    // ...
    return content;
  }
}),

Features

• improve performance
• improve resolving of script files specified w/o extension
• add resolving of file alias for scripts and styles
• update verbose output format to display output path and asset file separately
• update pug-loader to last version optimized for using with pug-plugin
• display a warning when used duplicate scripts or styles in same Pug file

Fixes

• resolving of absolute path using root context
• resolving of alias to file using root context
• allow to use url query in script source file
• verbose outputs data when asset is data URL

v3.0.0

⚠ BREAKING CHANGES

• Drop support for Node 12, minimum supported version is 14.18

  • Node 12 is End-of-Life.
  • Actual version of sass-loader 13.x requires Node 14.

• Defaults the embedded CSS extractor module is now enabled. For compatibility with external extractor, you can disable extractCss module:

new PugPlugin({
</tr></table> 

... (truncated)

Changelog

Sourced from pug-plugin's changelog.

4.1.0 (2022-08-03)

• feat: add the filename property to the pathData argument of the filename(pathData) function in entry object
• docs: add in readme recipes how to keep original folder structure in output directory

4.0.0 (2022-08-03)

• BREAKING CHANGE: default value PugPlugin.loader.option.method is now render instead of compile, because it makes sense in the vast majority of use cases.
  By compatibility issues (when the method was not specified), add the method option:

{
  loader: PugPlugin.loader,
  options: {
    method: 'compile', // now the default method is `render`
  }
},

• BREAKING CHANGE: the outputFile property of the ResourceInfo (the argument of postprocess function) was replaced with outputPath.
  By compatibility issues (when in the postprocess was used the outputFile), add in your postprocess function the code line:

new PugPlugin({
  postprocess: (content, info) => {
    const outputFile = path.join(info.outputPath, info.assetFile); // add this line to get the removed outputFile
    // ...
    return content;
  }
}),

• feat: add resolving of file alias for scripts and styles
• feat: improve resolving of script files specified w/o extension
• feat: improve performance
• feat: update verbose output format to display output path and asset file separately
• feat: update pug-loader to last version optimized for using with pug-plugin
• fix: allow to use url query in script source file
• fix: resolving of absolute path using root context
• fix: resolving of alias to file using root context
• refactor: optimize code
• docs: update readme with usage examples for render and compile methods

3.1.3 (2022-07-23)

• fix: issue by webpack serv/watch when Pug contains duplicate scripts
• fix: display warning when Pug contains duplicate scripts
• fix: verbose outputs data when asset is data URL

3.1.2 (2022-07-23)

• feat(experimental): display a warning when used duplicate scripts or styles in same Pug file
• fix: resolving of duplicate assets in difference style files processed via responsive-loader
• fix: auto publicPath for assets processed via responsive-loader

... (truncated)

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)