Skip to content
Flint
Blog

cpuValidity

Enforces that the cpu property is valid.

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

The rule checks that, if present, the cpu property is an array of non-empty strings.

Examples

Section titled “Examples”
5<3{d ivclassNa="meec-li">nt< sp ansty="le--0:#7FDBCA;--1:#096E">72"cp53<: sp ansty="le--0:#FF6A83;--1:#A248">48tr5<3}d ivclassNa="meco"><}d>
3de6E72"3F5<3: [ spans="tyle--0:#D9F5DD;--1:#11">1<111" spans="tyle--0:#C789D6;--1:#7C">568<6x64 spans="tyle--0:#D9F5DD;--1:#11">1<111" spans="tyle--0:#D6DEEB;--1:#40">3F<53, spans="tyle--0:#D9F5DD;--1:#11">1<111" spans="tyle--0:#C789D6;--1:#7C">56861<111" spans="tyle--0:#D6DEEB;--1:#40">33<"]>

When Not To Use It

Section titled “When Not To Use It”

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

Section titled “Related Rules”
  • cpuPresence - Enforces that the cpu property is present.

Further Reading

Section titled “Further Reading”

Equivalents in Other Linters

Section titled “Equivalents in Other Linters”