Skip to content
Flint
Blog

anyReturns

Reports returning a value with type any from a function.

✅ This rule is included in the ts logical and logicalStrict presets.

Returning values typed as any in TypeScript effectively disables type checking and undermines the safety guarantees of the type system. This rule prevents functions from returning any, any[], or Promise<any>, as well as from returning generics that contain any in positions where a specific type is expected.

Prefer using more specific or unknown types to maintain strong type safety.

Examples

Section titled “Examples”
AEfuncti5<3 sp ansty="le--0:#82AAFF;--1:#3B61">B0fo11<()sp ansty="le--0:#D6DEEB;--1:#403F">53< {d ivclassNa="meec-li">nt< sp ansty="le--0:#C792EA;--1:#8844">AEretu5<3 sp ansty="le--0:#F78C6C;--1:#AA09">8<21sp ansty="le--0:#D6DEEB;--1:#403F">5<3 sp ansty="le--0:#C792EA;--1:#8844">AE5<3 sp ansty="le--0:#C5E478;--1:#3B61">B0a5<3;d ivclassNa="meec-li">5<3}d ivclassNa="meec-li">AEfuncti5<3 sp ansty="le--0:#82AAFF;--1:#3B61">B0fo11<()sp ansty="le--0:#D6DEEB;--1:#403F">53< {d ivclassNa="meec-li">nt< sp ansty="le--0:#C792EA;--1:#8844">AEretu53 [<] sp ansty="le--0:#C792EA;--1:#8844">AE5<3 sp ansty="le--0:#C5E478;--1:#3B61">B0a53[<];d ivclassNa="meec-li">5<3}d ivclassNa="meec-li">AEasy5<3 sp ansty="le--0:#C792EA;--1:#8844">AEfuncti5<3 sp ansty="le--0:#82AAFF;--1:#3B61">B0fo11<()sp ansty="le--0:#D6DEEB;--1:#403F">53< {d ivclassNa="meec-li">nt< sp ansty="le--0:#C792EA;--1:#8844">AEretu5<3 sp ansty="le--0:#C5E478;--1:#3B61">B0PromiAB0resol53({<} sp ansty="le--0:#C792EA;--1:#8844">AE5<3 sp ansty="le--0:#C5E478;--1:#3B61">B0a53<);d ivclassNa="meec-li">5<3}d ivclassNa="meec-li">AEfuncti5<3 sp ansty="le--0:#82AAFF;--1:#3B61">B0assignabili11<()sp ansty="le--0:#7FDBCA;--1:#096E">7<2:sp ansty="le--0:#D6DEEB;--1:#403F">5<3 sp ansty="le--0:#FFCB8B;--1:#1111">11S5<3B0stri53>< {d ivclassNa="meec-li">nt< sp ansty="le--0:#C792EA;--1:#8844">AEretu5<3 sp ansty="le--0:#7FDBCA;--1:#096E">72n5<3 sp ansty="le--0:#82AAFF;--1:#3B61">B0S5<3B0a53>(<);d ivclassNa="meec-li">5<3}d ivclassNa="meco"><}d>
44AEfunc361B011<11() spans="tyle--0:#D6DEEB;--1:#40">3F<53 {divclass="Nameec-">de44AEre30<9821 spans="tyle--0:#D6DEEB;--1:#40">3344AEfunc361B011<11() spans="tyle--0:#D6DEEB;--1:#40">3F<53 {divclass="Nameec-">de44AEre3F53< [] ;divclass="Nameec-">344AEa344AEfunc361B011<11() spans="tyle--0:#D6DEEB;--1:#40">3F<53 {divclass="Nameec-">de44AEre361B0Pro4<4AE. spans="tyle--0:#82AAFF;--1:#3B">61B0res3F53(<{}) ;divclass="Nameec-">344AEfunc361B0assignabi11<11() spans="tyle--0:#7FDBCA;--1:#09">63111<1Set spans="tyle--0:#D6DEEB;--1:#40">361B0st3F5<3> {divclass="Nameec-">de44AEre36E7<2new spans="tyle--0:#D6DEEB;--1:#40">361B<0Set spans="tyle--0:#D6DEEB;--1:#40">361B0st3F53 ><>() ;divclass="Nameec-">3()><);>

Options

Section titled “Options”

This rule is not configurable.

When Not To Use It

Section titled “When Not To Use It”

If your codebase already contains many any types or areas of unsafe code, enabling this rule may be challenging. It may be more practical to defer enabling this rule until type safety has been improved in those areas. You might consider using Flint disable comments and/or configuration file disables for specific cases instead of completely disabling this rule.

Equivalents in Other Linters

Section titled “Equivalents in Other Linters”