enginesValidity

Enforces that the engines property is valid.

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

This rule checks that the engines property is an object with non-empty string values.

Examples

❌ Incorre

5<3{d ivclassNa="meec-li">nt< sp ansty="le--0:#7FDBCA;--1:#096E">72"engine53:< {d ivclassNa="meec-li">nt < sp ansty="le--0:#7FDBCA;--1:#096E">72"nod53<: sp ansty="le--0:#F78C6C;--1:#AA09">82<24d ivclassNa="meec-li">53< sp ansty="le--0:#D6DEEB;--1:#403F">5<3}d ivclassNa="meec-li">5<3}d ivclassNa="meco"><}d>

3de6E72"engi3F5<3: {divclass="Nameec-">dent< spans="tyle--0:#7FDBCA;--1:#09">6E72"n3F<53: spans="tyle--0:#D9F5DD;--1:#11">1<111" spans="tyle--0:#C789D6;--1:#7C">5686^24.<11.0 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 engines 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

• enginesPresence - Enforces that the engines property is present.

Further Reading

• npm: package.json > engines

Equivalents in Other Linters

• ESLint: package-json/valid-engines