documention doesn't match implementation #67

Activity

1. bjohansebas commented on Jan 16, 2026

   

   bjohansebas

   on Jan 16, 2026

   Member

   More actions

   In which part does it not match the documentation of this package?
2. krzysdz commented on Jan 18, 2026

   

   krzysdz

   on Jan 18, 2026

   Contributor

   More actions

   In which part does it not match the documentation of this package?

   1. types returns false, not undefined when there is no match

      • accepts/index.js

        Line 43 in 04c8970

        * the best match when true, otherwise `undefined`, in which

      • accepts/index.js

        Line 70 in 04c8970

        * // => undefined

   2. types description doesn't explicitly list a list of arguments as supported input, although it is supported and there are examples that show it (compare with the description in express)

      • accepts/index.js

        Lines 46 to 49 in 04c8970

        	* The `type` value may be a single mime type string
        	* such as "application/json", the extension name
        	* such as "json" or an array `["json", "html", "text/plain"]`. When a list
        	* or array is given the _best_ match, if any is returned.
3. jonchurch

   closed this as completedin #72on Jan 20, 2026