devDependenciesValidity

Enforces that the devDependencies property is valid.

✅ This rule is included in the package-json logical presets.

The rule checks that, if present, the devDependencies property is an object where each key is a valid package name and each value is a valid version range.

Examples

❌ Incorre

5<3{d ivclassNa="meec-li">nt< sp ansty="le--0:#7FDBCA;--1:#096E">72"devDependencie53:< {d ivclassNa="meec-li">nt < sp ansty="le--0:#7FDBCA;--1:#096E">72"invalid-versio53<: sp ansty="le--0:#D9F5DD;--1:#1111">1<1"sp ansty="le--0:#C789D6;--1:#7C56">86catalo1<1"d ivclassNa="meec-li">53< sp ansty="le--0:#D6DEEB;--1:#403F">5<3}d ivclassNa="meec-li">5<3}d ivclassNa="meco"><}d>

3de6E72"devDependenc3F5<3: {divclass="Nameec-">dent< spans="tyle--0:#7FDBCA;--1:#09">6E72"fi3F<53: spans="tyle--0:#D9F5DD;--1:#11">1<111" spans="tyle--0:#C789D6;--1:#7C">5686cata1<111" spans="tyle--0:#D6DEEB;--1:#40">3dent< spans="tyle--0:#7FDBCA;--1:#09">6E72"th4E4Df6E<72"" spans="tyle--0:#D6DEEB;--1:#40">3F<53: spans="tyle--0:#D9F5DD;--1:#11">1<111" spans="tyle--0:#C789D6;--1:#7C">5686^1<.2.3 spans="tyle--0:#D9F5DD;--1:#11">1<111" spans="tyle--0:#D6DEEB;--1:#40">3dent< spans="tyle--0:#7FDBCA;--1:#09">6E72"david-bo3F<53: spans="tyle--0:#D9F5DD;--1:#11">1<111" spans="tyle--0:#C789D6;--1:#7C">5<686* spans="tyle--0:#D9F5DD;--1:#11">1<111 "divclass="Nameec-">3F<53 spans="tyle--0:#D6DEEB;--1:#40">33< }>

When Not To Use It

If you don’t need compliance with npm’s devDependencies field specification, you can disable this rule. For example, if you use a different package manager that treats the field differently, this rule may not be correct for you.

Related Rules

• devDependenciesPresence - Enforces that the devDependencies property is present.

Further Reading

• npm: package.json > devDependencies

Equivalents in Other Linters

• ESLint: package-json/valid-devDependencies