Security News
tea.xyz Spam Plagues npm and RubyGems Package Registries
Tea.xyz, a crypto project aimed at rewarding open source contributions, is once again facing backlash due to an influx of spam packages flooding public package registries.
stylelint-test-rule-node
Advanced tools
Changelog
0.2.1
fixed
property to be allowed.stylelint
to ^16.0.1
in peer dependencies.Readme
A Stylelint rule tester using Node.js built-in test runner (node:test
).
Install the tester package alongside Stylelint:
npm install stylelint-test-rule-node stylelint --save-dev
First, write a test file for rules you want to test. For example:
// block-no-empty.test.js
import { testRule } from "stylelint-test-rule-node";
testRule({
ruleName: "block-no-empty",
config: true,
accept: [
{
code: "a { color: red }"
}
],
reject: [
{
code: "a {}",
message: "Unexpected empty block (block-no-empty)"
}
]
});
Then, run the test via node --test
:
$ node --test block-no-empty.test.js
...
▶ block-no-empty (28.773291ms)
ℹ tests 2
ℹ suites 7
ℹ pass 2
ℹ fail 0
ℹ cancelled 0
ℹ skipped 0
ℹ todo 0
ℹ duration_ms 158.194084
See also the type definitions for more details.
testRule
The testRule
function enables you to efficiently test your plugin using a schema.
For example, we can test a plugin that enforces and autofixes kebab-case class selectors:
// my-plugin.test.js
import { testRule } from "stylelint-test-rule-node";
import myPlugin from "./my-plugin.js";
const plugins = [myPlugin];
const {
ruleName,
rule: { messages }
} = myPlugin;
testRule({
plugins,
ruleName,
config: [true, { type: "kebab" }],
fix: true,
accept: [
{
code: ".class {}",
description: "simple class selector"
},
{
code: ".my-class {}",
description: "kebab class selector"
}
],
reject: [
{
code: ".myClass {}",
fixed: ".my-class {}",
description: "camel case class selector",
message: messages.expected(),
line: 1,
column: 1,
endLine: 1,
endColumn: 8
},
{
code: ".MyClass,\n.MyOtherClass {}",
fixed: ".my-class,\n.my-other-class {}",
description: "two pascal class selectors in a selector list",
warnings: [
{
message: messages.expected(),
line: 1,
column: 1,
endLine: 1,
endColumn: 8
},
{
message: messages.expected(),
line: 2,
column: 1,
endLine: 2,
endColumn: 13
}
]
}
]
});
testRuleConfigs
The testRuleConfigs
function enables you to test invalid configs for a rule.
For example:
import { testRuleConfigs } from "stylelint-test-rule-node";
testRuleConfigs({
plugins,
ruleName,
accept: [
{
config: "valid"
}
],
reject: [
{
config: "invalid"
},
{
config: [/invalid/],
description: "regex is not allowed"
}
]
});
FAQs
A Stylelint rule tester using Node.js built-in test runner.
The npm package stylelint-test-rule-node receives a total of 671 weekly downloads. As such, stylelint-test-rule-node popularity was classified as not popular.
We found that stylelint-test-rule-node demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Tea.xyz, a crypto project aimed at rewarding open source contributions, is once again facing backlash due to an influx of spam packages flooding public package registries.
Security News
As cyber threats become more autonomous, AI-powered defenses are crucial for businesses to stay ahead of attackers who can exploit software vulnerabilities at scale.
Security News
UnitedHealth Group disclosed that the ransomware attack on Change Healthcare compromised protected health information for millions in the U.S., with estimated costs to the company expected to reach $1 billion.