Gathering detailed insights and metrics for postcss-svgo-nightly
Gathering detailed insights and metrics for postcss-svgo-nightly
Gathering detailed insights and metrics for postcss-svgo-nightly
Gathering detailed insights and metrics for postcss-svgo-nightly
Un-Official nightly release for cssnano under name `cssnano-nightly`
npm install postcss-svgo-nightly
Typescript
Module System
Min. Node Version
Node Version
NPM Version
59.6
Supply Chain
94.6
Quality
73.5
Maintenance
50
Vulnerability
99.3
License
JavaScript (96.55%)
CSS (3.05%)
Shell (0.4%)
Total Downloads
2,885
Last Day
9
Last Week
18
Last Month
46
Last Year
441
1 Stars
65 Commits
1 Watchers
16 Branches
1 Contributors
Updated on Mar 04, 2023
Minified
Minified + Gzipped
Latest Version
0.8.4
Package Id
postcss-svgo-nightly@0.8.4
Unpacked Size
9.26 kB
Size
4.26 kB
File Count
5
NPM Version
6.14.6
Node Version
10.22.0
Cumulative downloads
Total Downloads
Last Day
0%
9
Compared to previous day
Last Week
20%
18
Compared to previous week
Last Month
-30.3%
46
Compared to previous month
Last Year
36.5%
441
Compared to previous year
4
In this, the package is named as postcss-svgo-nightly
In from this docs, you need to replace every
postcss-svgo --> postcss-svgo-nightly
Original Docs below
Optimise inline SVG with PostCSS.
With npm do:
npm install postcss-svgo --save
1h1 { 2 background: url('data:image/svg+xml;charset=utf-8,<?xml version="1.0" encoding="utf-8"?><!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd"><svg version="1.1" id="Layer_1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" xml:space="preserve"><circle cx="50" cy="50" r="40" fill="yellow" /></svg>'); 3} 4 5h2 { 6 background: url('data:image/svg+xml;base64,PD94bWwgdmVyc2lvbj0iMS4wIiBlbmNvZGluZz0idXRmLTgiPz48IURPQ1RZUEUgc3ZnIFBVQkxJQyAiLS8vVzNDLy9EVEQgU1ZHIDEuMS8vRU4iICJodHRwOi8vd3d3LnczLm9yZy9HcmFwaGljcy9TVkcvMS4xL0RURC9zdmcxMS5kdGQiPjxzdmcgdmVyc2lvbj0iMS4xIiBpZD0iTGF5ZXJfMSIgeG1sbnM9Imh0dHA6Ly93d3cudzMub3JnLzIwMDAvc3ZnIiB4bWxuczp4bGluaz0iaHR0cDovL3d3dy53My5vcmcvMTk5OS94bGluayIgeG1sOnNwYWNlPSJwcmVzZXJ2ZSI+PGNpcmNsZSBjeD0iNTAiIGN5PSI1MCIgcj0iNDAiIGZpbGw9InllbGxvdyIgLz48IS0tdGVzdCBjb21tZW50LS0+PC9zdmc+'); 7}
1h1 { 2 background: url('data:image/svg+xml;charset=utf-8,<svg xmlns="http://www.w3.org/2000/svg"><circle cx="50" cy="50" r="40" fill="%23ff0"/></svg>'); 3} 4 5h2 { 6 background: url('data:image/svg+xml;base64,PHN2ZyB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC9zdmciPjxjaXJjbGUgY3g9IjUwIiBjeT0iNTAiIHI9IjQwIiBmaWxsPSIjZmYwIi8+PC9zdmc+'); 7}
svgo([options])
Note that postcss-svgo is an asynchronous processor. It cannot be used like this:
1var result = postcss([ svgo() ]).process(css).css; 2console.log(result);
Instead make sure your PostCSS runner uses the asynchronous API:
1postcss([ svgo() ]).process(css).then(function (result) { 2 console.log(result.css); 3});
Type: boolean
Default: undefined
If true
, it will encode URL-unsafe characters such as <
, >
and &
;
false
will decode these characters, and undefined
will neither encode nor
decode the original input. Note that regardless of this setting, #
will
always be URL-encoded.
Optionally, you can customise the output by specifying the plugins
option. You
will need to provide the config in comma separated objects, like the example
below. Note that you can either disable the plugin by setting it to false
,
or pass different options to change the default behaviour.
1var postcss = require('postcss'); 2var svgo = require('postcss-svgo'); 3 4var opts = { 5 plugins: [{ 6 removeDoctype: false 7 }, { 8 removeComments: false 9 }, { 10 cleanupNumericValues: { 11 floatPrecision: 2 12 } 13 }, { 14 convertColors: { 15 names2hex: false, 16 rgb2hex: false 17 } 18 }] 19}; 20 21postcss([ svgo(opts) ]).process(css).then(function (result) { 22 console.log(result.css) 23});
You can view the full list of plugins here.
See the PostCSS documentation for examples for your environment.
See CONTRIBUTORS.md.
MIT © Ben Briggs
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
no dangerous workflow patterns detected
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
Found 0/30 approved changesets -- score normalized to 0
Reason
detected GitHub workflow tokens with excessive permissions
Details
Reason
no SAST tool detected
Details
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
dependency not pinned by hash detected -- score normalized to 0
Details
Reason
license file not detected
Details
Reason
security policy file not detected
Details
Reason
project is not fuzzed
Details
Reason
branch protection not enabled on development/release branches
Details
Reason
68 existing vulnerabilities detected
Details
Score
Last Scanned on 2025-06-23
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