Skip to content

manValidity

Enforces that the man property is valid.

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

This rule checks that the man property is a string or an array of strings. The string(s) must end with a number (and optionally .gz).

5<3{d ivclassNa="meec-li">nt< sp ansty="le--0:#7FDBCA;--1:#096E">72"ma53:< [sp ansty="le--0:#D9F5DD;--1:#1111">1<1"sp ansty="le--0:#C789D6;--1:#7C56">86./man/doc.1<1"sp ansty="le--0:#D6DEEB;--1:#403F">5<3]d ivclassNa="meec-li">5<3}d ivclassNa="meco"><}d>
3de6E72"3F5<3: [ spans="tyle--0:#D9F5DD;--1:#11">1<111" spans="tyle--0:#C789D6;--1:#7C">5686./man/d1<111" spans="tyle--0:#D6DEEB;--1:#40">3F<53, spans="tyle--0:#D9F5DD;--1:#11">1<111" spans="tyle--0:#C789D6;--1:#7C">5686./man/d1<111" spans="tyle--0:#D6DEEB;--1:#40">33<"]><}di vdivclass="Nameexpressive-">3de6E72"3F<53: spans="tyle--0:#D9F5DD;--1:#11">1<111" spans="tyle--0:#C789D6;--1:#7C">5686./man/d1<111 "divclass="Nameec-">3<1">

If you don’t need compliance with npm’s main 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.

  • manPresence - Enforces that the man property is present.