[dependabot]

Bumps @fullhuman/postcss-purgecss from 9.0.0 to 9.1.0.

Release notes

Sourced from @​fullhuman/postcss-purgecss's releases.

v9.1.0

PurgeCSS and its plugins now work with the bundlers in use today: Vite 8 and Rolldown, Next.js 16 with Turbopack, Rspack 1 and 2, webpack 5 and Parcel. See the package changelogs for the details, e.g. purgecss, @​fullhuman/postcss-purgecss, purgecss-webpack-plugin and rollup-plugin-purgecss.

Highlights

• Faster content scanning. Content files are read in parallel. With the new ContentCache, which the plugins use, a content file is only read and extracted again when it changed: with the PostCSS plugin, 20 CSS files over 1,081 content files went from 7.6 s to 1.6 s.
• Faster purging. Unused rules are removed in one pass after the walk, which gives the same output, about a third faster on large stylesheets; rejectedCss on Tailwind CSS 2 went from about 115 s to 0.5 s.
• Dev servers stay in sync. The PostCSS plugin adds dependency messages for the content files and globs, so Vite, Next.js, webpack and Rspack (postcss-loader) and Parcel purge the CSS again when the content changes, instead of serving stale CSS until a restart. New options dependencies and contentCache.
• CSS modules. The used classes of CSS modules are kept by the PostCSS plugin when postcss-modules runs first (Vite), and by the webpack plugin with mini-css-extract-plugin, CssExtractRspackPlugin, the native CSS of Rspack (including composes from another file) and webpack's experiments.css.
• purgecss-webpack-plugin works with Rspack without webpack installed, purges in processAssets, extracts the content once per compilation, watches the content files and fixes its source maps.
• rollup-plugin-purgecss works with Rolldown and Vite 8, where builds failed, creates the output directory, implements insert and honours contentFunction.

Changelog

Sourced from @​fullhuman/postcss-purgecss's changelog.

9.1.0

PurgeCSS and its plugins now work with the bundlers in use today: Vite 8 and Rolldown, Next.js 16 with Turbopack, Rspack 1 and 2, webpack 5 and Parcel. See the package changelogs for the details, e.g. purgecss, @​fullhuman/postcss-purgecss, purgecss-webpack-plugin and rollup-plugin-purgecss.

Highlights

• Faster content scanning. Content files are read in parallel. With the new ContentCache, which the plugins use, a content file is only read and extracted again when it changed: with the PostCSS plugin, 20 CSS files over 1,081 content files went from 7.6 s to 1.6 s.
• Faster purging. Unused rules are removed in one pass after the walk, which gives the same output, about a third faster on large stylesheets; rejectedCss on Tailwind CSS 2 went from about 115 s to 0.5 s.
• Dev servers stay in sync. The PostCSS plugin adds dependency messages for the content files and globs, so Vite, Next.js, webpack and Rspack (postcss-loader) and Parcel purge the CSS again when the content changes, instead of serving stale CSS until a restart. New options dependencies and contentCache.
• CSS modules. The used classes of CSS modules are kept by the PostCSS plugin when postcss-modules runs first (Vite), and by the webpack plugin with mini-css-extract-plugin, CssExtractRspackPlugin, the native CSS of Rspack (including composes from another file) and webpack's experiments.css.
• purgecss-webpack-plugin works with Rspack without webpack installed, purges in processAssets, extracts the content once per compilation, watches the content files and fixes its source maps.
• rollup-plugin-purgecss works with Rolldown and Vite 8, where builds failed, creates the output directory, implements insert and honours contentFunction.

Commits

• 38f7d07 chore: release 9.1.0 (#1589)
• e0f3dd4 feat: make the JS plugins work with 2026 bundlers (#1588)
• c122e13 docs: document the sourceMap option and the sourceMap result (#1586)
• 6ae41d9 docs: document how the PostCSS and webpack plugins load purgecss.config.js (#...
• 834d7ff docs: restyle the site in Lab Report, remove the ad, fix SEO and broken links...
• 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @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)

[netlify]

✅ Deploy Preview for gethinode-demo ready!

Name	Link
🔨 Latest commit	c69316f
🔍 Latest deploy log	https://app.netlify.com/projects/gethinode-demo/deploys/6af321da61ffe66cb235581d
😎 Deploy Preview	https://deploy-preview-2353--gethinode-demo.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[github-actions]

I'm approving this pull request because it includes a patch or minor update