Installations

npm install icss-replace-symbols

Pull Requests

Open

14

Total

83

Closed

51

Merged

18

Issues

Open

4

Total

9

Closed

5

Releases

5

v5.1.0

Published on 19 Nov 2020

v5.0.0

Published on 12 Oct 2020

v5.0.0-rc.0

Published on 21 Sept 2020

4.1.1

v4.1.1

Published on 29 May 2019

v4.1.0

Published on 26 Feb 2019

View all 5 releases

Developer

css-modules

Developer Guide

BETA

Module System

CommonJS

Min. Node Version

Typescript Support

No

Node Version

7.6.0

NPM Version

4.1.2 Statistics

23 Stars

67 Commits

15 Forks

6 Watching

39 Branches

15 Contributors

Updated on 13 Nov 2023

Languages

JavaScript (100%)

Total Downloads

Cumulative downloads

Total Downloads

1,149,027,201

Last day

-6.5%

463,219

Compared to previous day

Last week

1.1%

2,716,020

Compared to previous week

Last month

20.3%

11,190,041

Compared to previous month

Last year

-15.9%

118,822,805

Compared to previous year

Daily Downloads

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dev Dependencies

7

babel-cli babel-preset-es2015 babel-register chokidar mocha postcss standard

Versions

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 2024-11-25

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