Douglas Wilson

Thanks! I left a comment there. Let's give 30 days from now on that issue if it's not resolved and then we'll go with the reaching into internals solution of...

Hi! We are actually actively working on this problem :) This module depends on the `negotiator` module to do the work, and we have a PR https://github.com/jshttp/negotiator/pull/40 that is trying...

> We could ideally provide the folliowing as type params As in, input to this library? If that is that you're suggesting, we already do offer that: ``` js typeis(req,...

Hi @bazwilliams , sorry this went stale, but it looks like I was waiting for clarification to my question. Can you clarify?

Ok, but you still haven't cleared up to me what you want me to do. Can you elaborate more on what you mean in https://github.com/jshttp/type-is/issues/14#issuecomment-111172617 ?

Gotcha, makes sense now. So yes, this library doesn't let you match on the parameters. The only way you can do it currently is to include the `content-type` library to...

I am fine to add more platforms than Node.js if that does not end up forking the code too much. If someone would like to put a pull request together...

Hi @creeperyang, yes, I agree. The weird discrepancy comes from how everything got bundled together: when you specify a file extension, instead of doing what seems more logical, and what...

Hi! So actually thinking about this for a bit, I think that at some point (would need a major version bump), just using extensions at all should mean "any type...

To add to this (I'm typically the person around various things like `http-errors`): 1. I am happy to perform some kind of critical patch against the previous major version of...