Skip to content
Flint
Blog

publishConfigRedundancy

Reports publishConfig.access fields that do not affect unscoped packages.

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

This rule reports publishConfig.access fields in unscoped packages. Unscoped npm packages are always published with public access, so this field only changes publishing behavior for scoped packages.

Examples

Section titled “Examples”
5<3{d ivclassNa="meec-li">nt< sp ansty="le--0:#7FDBCA;--1:#096E">72"nam53<: sp ansty="le--0:#D9F5DD;--1:#1111">1<1"sp ansty="le--0:#C789D6;--1:#7C56">86my-packa1<1"sp ansty="le--0:#D6DEEB;--1:#403F">5<3,d ivclassNa="meec-li">nt< sp ansty="le--0:#7FDBCA;--1:#096E">72"publishConfi53:< {d ivclassNa="meec-li">nt < sp ansty="le--0:#7FDBCA;--1:#096E">72"acces53<: sp ansty="le--0:#D9F5DD;--1:#1111">1<1"sp ansty="le--0:#C789D6;--1:#7C56">86publ1<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>5<3{d ivclassNa="meec-li">nt< sp ansty="le--0:#7FDBCA;--1:#096E">72"nam53<: sp ansty="le--0:#D9F5DD;--1:#1111">1<1"sp ansty="le--0:#C789D6;--1:#7C56">86my-packa1<1"sp ansty="le--0:#D6DEEB;--1:#403F">5<3,d ivclassNa="meec-li">nt< sp ansty="le--0:#7FDBCA;--1:#096E">72"publishConfi53:< {d ivclassNa="meec-li">nt < sp ansty="le--0:#7FDBCA;--1:#096E">72"acces53<: sp ansty="le--0:#D9F5DD;--1:#1111">1<1"sp ansty="le--0:#C789D6;--1:#7C56">86restrict1<1"sp ansty="le--0:#D6DEEB;--1:#403F">5<3,d ivclassNa="meec-li">nt < sp ansty="le--0:#7FDBCA;--1:#096E">72"registr53<: sp ansty="le--0:#D9F5DD;--1:#1111">1<1"sp ansty="le--0:#C789D6;--1:#7C56">86https://registry.npmjs.or1<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"n3F<53: spans="tyle--0:#D9F5DD;--1:#11">1<111" spans="tyle--0:#C789D6;--1:#7C">5686@scope/my-pac1<111" spans="tyle--0:#D6DEEB;--1:#40">3de6E72"publishCon3F5<3: {divclass="Nameec-">dent< spans="tyle--0:#7FDBCA;--1:#09">6E72"acc3F<53: spans="tyle--0:#D9F5DD;--1:#11">1<111" spans="tyle--0:#C789D6;--1:#7C">5686pu1<111 "divclass="Nameec-">3F<53 spans="tyle--0:#D6DEEB;--1:#40">33< }><}di vdivclass="Nameexpressive-">3de6E72"n3F<53: spans="tyle--0:#D9F5DD;--1:#11">1<111" spans="tyle--0:#C789D6;--1:#7C">5686my-pac1<111" spans="tyle--0:#D6DEEB;--1:#40">3de6E72"publishCon3F5<3: {divclass="Nameec-">dent< spans="tyle--0:#7FDBCA;--1:#09">6E72"regis3F<53: spans="tyle--0:#D9F5DD;--1:#11">1<111" spans="tyle--0:#C789D6;--1:#7C">5686https://registry.npmjs.1<111 "divclass="Nameec-">3F<53 spans="tyle--0:#D6DEEB;--1:#40">33< }>

When Not To Use It

Section titled “When Not To Use It”

If a package intentionally keeps publishConfig.access as documentation for a future move to a scoped package, this rule might not be for you.

Further Reading

Section titled “Further Reading”

Equivalents in Other Linters

Section titled “Equivalents in Other Linters”