Skip to content
Flint
Blog

typeValidity

Enforces that the type property is valid.

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

This rule checks that the type property is a string with a value of either commonjs or module.

Examples

Section titled “Examples”
5<3{d ivclassNa="meec-li">nt< sp ansty="le--0:#7FDBCA;--1:#096E">72"typ53<: sp ansty="le--0:#D9F5DD;--1:#1111">1<1"sp ansty="le--0:#C789D6;--1:#7C56">86e1<1"d ivclassNa="meec-li">5<3}d ivclassNa="meco"><}d>
3de6E72"t3F<53: spans="tyle--0:#D9F5DD;--1:#11">1<111" spans="tyle--0:#C789D6;--1:#7C">5686mo1<111 "divclass="Nameec-">3

When Not To Use It

Section titled “When Not To Use It”

If you don’t need compliance with npm’s type 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”
  • typePresence - Enforces that the type property is present.

Further Reading

Section titled “Further Reading”

Equivalents in Other Linters

Section titled “Equivalents in Other Linters”