npmpackage.info

Gathering detailed insights and metrics for @stylelint/postcss-css-in-js

@stylelint/postcss-css-in-js

PostCSS syntax for parsing CSS in JS literals

0.38.0

MIT

JavaScript

280.02 kB

292,771,725 3.2

Installations

npm install @stylelint/postcss-css-in-js

Developer Guide

BETA

Typescript

No

Module System

CommonJS

Node Version

16.14.2

NPM Version

8.8.0 Pull Requests

Open

0

Total

302

Closed

178

Merged

124

Issues

Open

0

Total

0

Closed

0

Releases

0.38.0

Published on 03 May 2022

0.37.3

Published on 02 May 2022

0.37.2

Published on 12 Jul 2020

0.37.1

Published on 11 Apr 2020

0.37.0

Published on 06 Apr 2020

View all 5 releases

Contributors

Unable to fetch Contributors

View all 20 contributors

Languages

JavaScript

Shell

JavaScript (99.86%)

Shell (0.14%)

Developer

stylelint

Download Statistics

Total Downloads

292,771,725

Last Day

134,906

Last Week

638,675

Last Month

2,952,888

Last Year

42,653,691

GitHub Statistics

41 Stars

326 Commits

18 Forks

6 Watching

9 Branches

20 Contributors

Bundle Size

1.13 MB

Minified

280.02 kB

Minified + Gzipped

Bundlephobia

Maintainers

Package Meta Information

Latest Version

0.38.0

Package Id

@stylelint/postcss-css-in-js@0.38.0

Unpacked Size

39.55 kB

Size

12.31 kB

File Count

NPM Version

8.8.0

Node Version

16.14.2

Total Downloads

Cumulative downloads

Total Downloads

292,771,725

Last day

-12.5%

134,906

Compared to previous day

Last week

-18%

638,675

Compared to previous week

Last month

-2.1%

2,952,888

Compared to previous month

Last year

-25.4%

42,653,691

Compared to previous year

Daily Downloads

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dependencies

@babel/core

Peer Dependencies

postcss postcss-syntax

Dev Dependencies

Versions

PostCSS CSS-in-JS Syntax

PostCSS syntax for parsing CSS in JS literals:

Getting Started

First thing's first, install the module:

npm install postcss-syntax @stylelint/postcss-css-in-js --save-dev

Use Cases

1const postcss = require("postcss");
2const stylelint = require("stylelint");
3const syntax = require("postcss-syntax");
4postcss([stylelint({ fix: true })])
5  .process(source, { syntax: syntax })
6  .then(function (result) {
7    // An alias for the result.css property. Use it with syntaxes that generate non-CSS output.
8    result.content;
9  });

input:

1import glm from "glamorous";
2const Component1 = glm.a({
3  flexDirectionn: "row",
4  display: "inline-block",
5  color: "#fff"
6});

output:

1import glm from "glamorous";
2const Component1 = glm.a({
3  color: "#fff",
4  display: "inline-block",
5  flexDirectionn: "row"
6});

Advanced Use Cases

Add support for more css-in-js package:

1const syntax = require("postcss-syntax")({
2  "i-css": (index, namespace) => namespace[index + 1] === "addStyles",
3  "styled-components": true
4});

See: postcss-syntax

Style Transformations

The main use case of this plugin is to apply PostCSS transformations to CSS code in template literals & styles as object literals.

No vulnerabilities found.

10

Dangerous-Workflow

Determines if the project's GitHub Action workflows avoid dangerous patterns.

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.

4

Code-Review

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

4

Security-Policy

Determines if the project has published a security policy.

2

Pinned-Dependencies

Determines if the project has declared and pinned the dependencies of its build process.

0

CII-Best-Practices

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

0

Maintained

Determines if the project is "actively maintained".

0

Token-Permissions

Determines if the project's workflows follow the principle of least privilege.

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

3.2

/10

Last Scanned on 2025-01-20

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