npmpackage.info

Gathering detailed insights and metrics for icss-utils

Other packages similar to icss-utils

@types/icss-utils

5.1.2

TypeScript definitions for icss-utils

Gathering detailed insights and metrics for icss-utils

icss-utils - 5.1.0 | npmpackage.info

icss-utils

Search & replace tokens during the linking stage of ICSS loading

5.1.0

ISC

JavaScript

1.9

Installations

npm install icss-utils

Developer Guide

BETA

Typescript

No

Module System

CommonJS

Min. Node Version

^10 || ^12 || >= 14

Node Version

12.19.0

NPM Version

6.14.8 Score

98.6

Supply Chain

98.2

Quality

80.7

Maintenance

100

Vulnerability

100

License

Pull Requests

Open

14

Total

83

Closed

51

Merged

18

Issues

Open

4

Total

9

Closed

5

Releases

v5.1.0

Updated on Nov 19, 2020

v5.0.0

Updated on Oct 12, 2020

v5.0.0-rc.0

Updated on Sep 21, 2020

4.1.1

v4.1.1

Updated on May 29, 2019

v4.1.0

Updated on Feb 26, 2019

View All 5 releases

Languages

JavaScript

JavaScript (100%)

Developer

css-modules

Download Statistics

Total Downloads

Last Day

Last Week

Last Month

Last Year

GitHub Statistics

ISC License

22 Stars

67 Commits

15 Forks

5 Watchers

39 Branches

15 Contributors

Updated on Jan 04, 2025

Maintainers

View All 15 Contributors

Package Meta Information

Latest Version

5.1.0

Package Id

icss-utils@5.1.0

Size

3.93 kB

NPM Version

6.14.8

Node Version

12.19.0

Published on

Nov 19, 2020

Total Downloads

Cumulative downloads

Total Downloads

NaN

Last Day

NaN

Compared to previous day

Last Week

NaN

Compared to previous week

Last Month

NaN

Compared to previous month

Last Year

NaN

Compared to previous year

Weekly Downloads

Monthly Downloads

Yearly Downloads

Peer Dependencies

postcss

Dev Dependencies

coveralls eslint eslint-config-prettier husky jest lint-staged postcss prettier

ICSS Utils

replaceSymbols

Governs the way tokens are searched & replaced during the linking stage of ICSS loading.

This is broken into its own module in case the behaviour needs to be replicated in other PostCSS plugins (i.e. CSS Modules Values)

1import { replaceSymbols, replaceValueSymbols } from "icss-utils";
2
3replaceSymbols(css, replacements);
4replaceValueSymbols(string, replacements);

Where:

css is the PostCSS tree you're working with
replacements is an JS object of symbol: "replacement" pairs, where all occurrences of symbol are replaced with replacement.

A symbol is a string of alphanumeric, - or _ characters. A replacement can be any string. They are replaced in the following places:

In the value of a declaration, i.e. color: my_symbol; or box-shadow: 0 0 blur spread shadow-color
In a media expression i.e. @media small {} or @media screen and not-large {}

extractICSS(css, removeRules = true, mode = 'auto')

Extracts and remove (if removeRules is equal true) from PostCSS tree :import, @icss-import, :export and @icss-export statements.

1import postcss from "postcss";
2import { extractICSS } from "icss-utils";
3
4const css = postcss.parse(`
5  :import(colors) {
6    a: b;
7  }
8  :export {
9    c: d;
10  }
11`);
12
13extractICSS(css);
14/*
15  {
16    icssImports: {
17      colors: {
18        a: 'b'
19      }
20    },
21    icssExports: {
22      c: 'd'
23    }
24  }
25*/

By default both the pseudo and at-rule form of the import and export statements will be removed. Pass the mode option to limit to only one type.

createICSSRules(icssImports, icssExports, mode = 'rule')

Converts icss imports and exports definitions to postcss ast

1createICSSRules(
2  {
3    colors: {
4      a: "b",
5    },
6  },
7  {
8    c: "d",
9  },
10  // Need pass `rule` and `decl` from postcss
11  // Please look at `Step 4` https://evilmartians.com/chronicles/postcss-8-plugin-migration
12  postcss
13);

By default it will create pseudo selector rules (:import and :export). Pass at-rule for mode to instead generate @icss-import and @icss-export, which may be more resilient to post processing by other tools.

License

ISC

Glen Maddern, Bogdan Chadkin and Evilebottnawi 2015-present.

No vulnerabilities found.

10

Binary-Artifacts

Determines if the project has generated executable (binary) artifacts in the source repository.

10

License

Determines if the project has defined a license.

1

Code-Review

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

0

Maintained

Determines if the project is "actively maintained".

0

CII-Best-Practices

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

0

Security-Policy

Determines if the project has published a security policy.

0

Fuzzing

Determines if the project uses fuzzing.

0

Branch-Protection

Determines if the default and release branches are protected with GitHub's branch protection settings.

0

SAST

Determines if the project uses static code analysis.

0

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

Score

1.9

/10

Last Scanned on 2025-07-07

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