restify

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

@param 'options': Object → { name?: string; dtrace?: boolean; router?: Router; log?:.... JSDoc uses generic "object" but TypeScript infers a specific shape. Consider using @typedef to document the object structure.

@param 'opts': Object → { log: any; event: string; context?: Function; server?: a.... JSDoc uses generic "object" but TypeScript infers a specific shape. Consider using @typedef to document the object structure.

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

@param 'opts': Object → { limit?: number; max?: number; interval?: number; halfLi.... JSDoc uses generic "object" but TypeScript infers a specific shape. Consider using @typedef to document the object structure.

@param 'opts': Object → { limit: number; err: Error; server: Function; }. JSDoc uses generic "object" but TypeScript infers a specific shape. Consider using @typedef to document the object structure.

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

@param 'opts': Object → { headers: string[]; }. JSDoc uses generic "object" but TypeScript infers a specific shape. Consider using @typedef to document the object structure.

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

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

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

@param 'opts': Object → { absoluteHeader?: string; startHeader: string; timeoutHe.... JSDoc uses generic "object" but TypeScript infers a specific shape. Consider using @typedef to document the object structure.

@param 'options': Object → { headers?: any[]; properties?: any; serializers?: any; l.... JSDoc uses generic "object" but TypeScript infers a specific shape. Consider using @typedef to document the object structure.

@param 'opts': Object → { maxAge?: number; etag?: boolean; setHeaders?: Function; }. JSDoc uses generic "object" but TypeScript infers a specific shape. Consider using @typedef to document the object structure.

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

@param 'options': Object → { burst: number; rate: number; ip?: boolean; username?: b.... JSDoc uses generic "object" but TypeScript infers a specific shape. Consider using @typedef to document the object structure.

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

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

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

@param 'options': Object → { name: string; dtrace?: boolean; router: Router; log: an.... JSDoc uses generic "object" but TypeScript infers a specific shape. Consider using @typedef to document the object structure.