Gathering detailed insights and metrics for nuxt-purgecss
Gathering detailed insights and metrics for nuxt-purgecss
Drop superfluous CSS! A neat PurgeCSS wrapper for Nuxt.js
Installations
npm install nuxt-purgecssDeveloper Guide
BETA
Typescript
Yes
Module System
ESM
Node Version
16.14.0
NPM Version
8.19.2
Score
72.4
Supply Chain
88.9
Quality
73.1
Maintenance
100
Vulnerability
97.6
License
Languages
5
TypeScript
JavaScript
Vue
CSS
Shell
TypeScript (70.49%)
JavaScript (17.99%)
Vue (7.96%)
CSS (2.29%)
Shell (1.28%)
Developer
Developmint
Download Statistics
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
GitHub Statistics
MIT License
490 Stars
91 Commits
20 Forks
4 Watchers
15 Branches
12 Contributors
Updated on Jul 16, 2025
Maintainers
1
Package Meta Information
Latest Version
2.0.0
Package Id
nuxt-purgecss@2.0.0
Unpacked Size
12.95 kB
Size
5.23 kB
File Count
8
NPM Version
8.19.2
Node Version
16.14.0
Total Downloads
Cumulative downloads
Total Downloads
NaN
Last Day
0%
NaN
Compared to previous day
Last Week
0%
NaN
Compared to previous week
Last Month
0%
NaN
Compared to previous month
Last Year
0%
NaN
Compared to previous year
Weekly Downloads
Monthly Downloads
Yearly Downloads
Nuxt PurgeCSS - Drop superfluous CSS!
Features
- Remove unneeded CSS with ease
- Sane default settings
- Built on top of purgecss
- Nuxt 2 and Nuxt 3 support (Use v1.0.0 for Nuxt2 support for now)
- Fully tested!
Setup
- Add
nuxt-purgecssdependency to your project
1yarn add --dev nuxt-purgecss # or npm install --save-dev nuxt-purgecss
- Add
nuxt-purgecssto themodulessection ofnuxt.config.{js,ts}
1export default { 2 modules: [ 3 // Simple usage 4 'nuxt-purgecss', 5 6 // With options 7 ['nuxt-purgecss', { /* module options */ }], 8 ] 9}
:warning: If you are using Nuxt 2, please use version 1 of the module.
Options
Defaults
Before diving into the individual attributes, please have a look at the default settings of the module.
The defaults will scan all your .vue, .js and .ts files in the common Nuxt folders, as well as checking your nuxt.config.js (or .ts) for used classes.
Furthermore, typical classes (like these needed for transitions, the nuxt link ones or those set when using scoped styles) are whitelisted already.
These settings should be a good foundation for a variety of projects.
Properties in-depth
enabled
- Type:
Boolean - Default:
!nuxt.options.dev(Disabled duringnuxt dev, enabled otherwise)
Enables the module when set to true.
PurgeCSS options
Please read the PurgeCSS docs for information about PurgeCSS-related information.
Examples
Default setup
1// nuxt.config.js 2export default { 3 modules: [ 4 'nuxt-purgecss', 5 ] 6}
Customize options
1//nuxt.config.js 2export default { 3 modules: [ 4 'nuxt-purgecss', 5 ], 6 7 purgecss: { 8 enabled: true, // Always enable purgecss 9 safelist: ['my-class'], // Add my-class token to the safelist (e.g. .my-class) 10 } 11}
Caveats
- Don't forget to add paths to pages and components that are not part the common folders (e.g. third party packages)
- The default generated 500 and 404 pages will be purged by default. Please ensure you have an appropriate error layout
- Do not use the old
>>>or::v-deepsyntax. Instead, go for:deep
Migrating from v1.x
:warning: If you use Nuxt 2, you can't update to v2.x (yet?)
- The webpack mode has been removed, as Nuxt 3 supports Vite and webpack. This way, the logic is unified to use the PostCSS plugin of PurgeCSS. There is no
modeanymore - The config merging logic of v1 has been removed in favor of using
defu. Instead of using functions, write your values as usual and they will be merged. - PurgeCSS has been bumped from v2.x to v5.x - Please check the current config options
- Change the module key has been changed to just
purgecss. - In addition to
enabled, all purgecss configurations can be written directly into thepurgecssobject. - Eventually, check out the playground of the module and the [current defaults](at the default settings)!
License
Copyright (c) Alexander Lichter
No vulnerabilities found.
Reason
no dangerous workflow patterns detected
Reason
no binaries found in the repo
Reason
license file detected
Details
- Info: project has a license file: LICENSE:0
- Info: FSF or OSI recognized license: MIT License: LICENSE:0
Reason
Found 1/25 approved changesets -- score normalized to 0
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
detected GitHub workflow tokens with excessive permissions
Details
- Warn: no topLevel permission defined: .github/workflows/ci.yml:1
- Info: no jobLevel write permissions found
Reason
dependency not pinned by hash detected -- score normalized to 0
Details
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:21: update your workflow using https://app.stepsecurity.io/secureworkflow/Developmint/nuxt-purgecss/ci.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:26: update your workflow using https://app.stepsecurity.io/secureworkflow/Developmint/nuxt-purgecss/ci.yml/main?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:29: update your workflow using https://app.stepsecurity.io/secureworkflow/Developmint/nuxt-purgecss/ci.yml/main?enable=pin
- Warn: third-party GitHubAction not pinned by hash: .github/workflows/ci.yml:48: update your workflow using https://app.stepsecurity.io/secureworkflow/Developmint/nuxt-purgecss/ci.yml/main?enable=pin
- Info: 0 out of 3 GitHub-owned GitHubAction dependencies pinned
- Info: 0 out of 1 third-party GitHubAction dependencies pinned
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
- Warn: no security policy file detected
- Warn: no security file to analyze
- Warn: no security file to analyze
- Warn: no security file to analyze
Reason
project is not fuzzed
Details
- Warn: no fuzzer integrations found
Reason
branch protection not enabled on development/release branches
Details
- Warn: branch protection not enabled for branch 'main'
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
- Warn: 0 commits out of 30 are checked with a SAST tool
Reason
55 existing vulnerabilities detected
Details
- Warn: Project is vulnerable to: GHSA-968p-4wvh-cqc8
- Warn: Project is vulnerable to: GHSA-67hx-6x53-jw92
- Warn: Project is vulnerable to: GHSA-h5c3-5r3r-rr8q
- Warn: Project is vulnerable to: GHSA-rmvr-2pp2-xj38
- Warn: Project is vulnerable to: GHSA-xx4v-prfh-6cgc
- Warn: Project is vulnerable to: GHSA-v6h2-p8h4-qcjw
- Warn: Project is vulnerable to: GHSA-grv7-fg5c-xmjg
- Warn: Project is vulnerable to: GHSA-3xgq-45jj-v275
- Warn: Project is vulnerable to: GHSA-67mh-4wv8-2f99
- Warn: Project is vulnerable to: GHSA-jchw-25xp-jwwc
- Warn: Project is vulnerable to: GHSA-cxjh-pqwp-8mfp
- Warn: Project is vulnerable to: GHSA-4q6p-r6v2-jvc5
- Warn: Project is vulnerable to: GHSA-rc47-6667-2j5j
- Warn: Project is vulnerable to: GHSA-78xj-cgh5-2h22
- Warn: Project is vulnerable to: GHSA-2p57-rm9w-gvfp
- Warn: Project is vulnerable to: GHSA-p6mc-m468-83gw
- Warn: Project is vulnerable to: GHSA-35jh-r3h4-6jhm
- Warn: Project is vulnerable to: GHSA-952p-6rrq-rcjv
- Warn: Project is vulnerable to: GHSA-mwcw-c2x4-8c55
- Warn: Project is vulnerable to: GHSA-8g77-54rh-46hx
- Warn: Project is vulnerable to: GHSA-7fh5-64p2-3v2j
- Warn: Project is vulnerable to: GHSA-gcx4-mw62-g8wm
- Warn: Project is vulnerable to: GHSA-c2qf-rxjj-qqgw
- Warn: Project is vulnerable to: GHSA-m6fv-jmcg-4jfg
- Warn: Project is vulnerable to: GHSA-cm22-4g7w-348p
- Warn: Project is vulnerable to: GHSA-f5x3-32g6-xq36
- Warn: Project is vulnerable to: GHSA-5r9g-qh6m-jxff
- Warn: Project is vulnerable to: GHSA-r6ch-mqf9-qc9w
- Warn: Project is vulnerable to: GHSA-wqq4-5wpv-mx2g
- Warn: Project is vulnerable to: GHSA-3787-6prv-h9w3
- Warn: Project is vulnerable to: GHSA-9qxr-qj54-h672
- Warn: Project is vulnerable to: GHSA-m4v8-wqvr-p9f7
- Warn: Project is vulnerable to: GHSA-c76h-2ccp-4975
- Warn: Project is vulnerable to: GHSA-cxrh-j4jr-qwg3
- Warn: Project is vulnerable to: GHSA-353f-5xf4-qw67
- Warn: Project is vulnerable to: GHSA-c24v-8rfc-w8vw
- Warn: Project is vulnerable to: GHSA-8jhw-289h-jh2g
- Warn: Project is vulnerable to: GHSA-64vr-g452-qvp3
- Warn: Project is vulnerable to: GHSA-9cwx-2883-4wfx
- Warn: Project is vulnerable to: GHSA-vg6x-rcgg-rjx6
- Warn: Project is vulnerable to: GHSA-x574-m823-4x7w
- Warn: Project is vulnerable to: GHSA-4r4m-qw57-chr8
- Warn: Project is vulnerable to: GHSA-xcj6-pq6g-qj4x
- Warn: Project is vulnerable to: GHSA-356w-63v5-8wf4
- Warn: Project is vulnerable to: GHSA-859w-5945-r5v3
- Warn: Project is vulnerable to: GHSA-7jxr-cg7f-gpgv
- Warn: Project is vulnerable to: GHSA-xj72-wvfv-8985
- Warn: Project is vulnerable to: GHSA-ch3r-j5x3-6q2m
- Warn: Project is vulnerable to: GHSA-p5gc-c584-jj6v
- Warn: Project is vulnerable to: GHSA-whpj-8f3w-67p5
- Warn: Project is vulnerable to: GHSA-cchq-frgv-rjh5
- Warn: Project is vulnerable to: GHSA-g644-9gfx-q4q4
- Warn: Project is vulnerable to: GHSA-j8xg-fqg3-53r7
- Warn: Project is vulnerable to: GHSA-3h5v-q93c-6h6q
- Warn: Project is vulnerable to: GHSA-f9xv-q969-pqx4
Score
2.5
/10
Last Scanned on 2025-07-14
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More