55
Files Analyzed
8
Issues Found
1
Files with Issues

Issues by Rule

tjd/accurate-jsdoc
8

Issues by File

lodash.js 8 issues
9693:34 accurate-jsdoc

@param 'iteratees': Array[]|Function[]|Object[]|string[] → any[] | string[] | Function[] | any[][]. Types differ. Run with --fix to update JSDoc, or verify the intended type.

10411:35 accurate-jsdoc

@param 'options': Object → { leading?: boolean; maxWait?: number; trailing?: boolean; }. JSDoc uses generic "object" but TypeScript infers a specific shape. Consider using @typedef to document the object structure.

11004:35 accurate-jsdoc

@param 'options': Object → { leading?: boolean; trailing?: boolean; }. JSDoc uses generic "object" but TypeScript infers a specific shape. Consider using @typedef to document the object structure.

12983:5 accurate-jsdoc

@returns: string|undefined → string. JSDoc includes null/undefined but TypeScript infers the value is always present. Either the code guarantees a value, or add runtime checks.

13022:5 accurate-jsdoc

@returns: string|undefined → string. JSDoc includes null/undefined but TypeScript infers the value is always present. Either the code guarantees a value, or add runtime checks.

14877:31 accurate-jsdoc

@param 'options': Object → { escape?: RegExp; evaluate?: RegExp; imports?: any; inte.... JSDoc uses generic "object" but TypeScript infers a specific shape. Consider using @typedef to document the object structure.

15185:31 accurate-jsdoc

@param 'options': Object → { length?: number; omission?: string; separator?: string .... JSDoc uses generic "object" but TypeScript infers a specific shape. Consider using @typedef to document the object structure.

15817:36 accurate-jsdoc

@param 'options': Object → { chain?: boolean; }. JSDoc uses generic "object" but TypeScript infers a specific shape. Consider using @typedef to document the object structure.

Analyzed: 2/3/2026