Skip to content

chore(release): new release - #307

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
changeset-release/main
Open

chore(release): new release#307
github-actions[bot] wants to merge 1 commit into
mainfrom
changeset-release/main

Conversation

@github-actions

@github-actions github-actions Bot commented Sep 7, 2026

Copy link
Copy Markdown

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

diagnostics-webpack-plugin@1.0.0

Major Changes

  • quiet is gone: reportAs says what a check reports its results as, one value covering its errors and its warnings alike and an object setting them apart, so quiet: true is reportAs: { warnings: false }. (by @alexander-akait in #317)

  • Renamed from eslint-webpack-plugin and merged with stylelint-webpack-plugin: one plugin runs every linter through the checks option, new DiagnosticsPlugin({ checks: [{ use: "eslint" }, { use: "stylelint" }] }). Errors are reported as webpack errors and warnings as webpack warnings, with reportAs deciding what each is reported as; stylelint must be 17 or later. See the migration guides in the README. (by @alexander-akait in #306)

  • Dropped Node.js 20, which is end-of-life. The minimum is now Node.js >= 22.12.0. (by @alexander-akait in #309)

  • Rewritten as ECMAScript modules. The package is now "type": "module" and declares an exports field, shipping an ESM build next to a CommonJS one, so import DiagnosticsPlugin from "diagnostics-webpack-plugin" and require("diagnostics-webpack-plugin") both keep working. (by @alexander-akait in #308)

  • emitError, emitWarning, failOnError and failOnWarning are one reportAs option taking "error", "warning" or false: it says what a check reports its results as, and reporting one as a webpack error is what fails the build. Left unset each result keeps its own severity, quiet still drops the warnings, and the build is no longer aborted from inside the plugin. See the migration table in the README. (by @alexander-akait in #315)

Minor Changes

  • Added ESLint bulk suppressions. applySuppressions and suppressionsLocation reach the ESLint class as they are on ESLint 10, and on ESLint 9.24 and later the plugin applies the suppressions itself, since ESLint only wires them into its CLI there. (by @alexander-akait in #311)

  • Option validation now runs from webpack's compiler.hooks.validate, so a mistake is reported where webpack validates the rest of the configuration and validate: false turns it off. Where webpack predates the hook, in 5.106, the plugin validates as it did before. (by @alexander-akait in #313)

Patch Changes

  • Lint only the files webpack rebuilt, reporting the rest from the previous compilation, and start linting while the module graph is still being built. (by @alexander-akait in #319)

  • Replace globby, micromatch and normalize-path with tinyglobby and picomatch, and compile the file matchers once per check rather than on every module. (by @alexander-akait in #316)

The entries below belong to eslint-webpack-plugin, which this package
was renamed from. It is published as diagnostics-webpack-plugin from
1.0.0 on, so its versions start over.

@github-actions
github-actions Bot force-pushed the changeset-release/main branch 10 times, most recently from f3e097d to f797a03 Compare September 8, 2026 10:50
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from f797a03 to d6b5add Compare September 8, 2026 13:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants