This release adds a small but likely very useful feature allowing people to specify a user agent as part of the detect function call, e.g.
const uaString = '...'; // sourced from somewhere intelligent
detect(uaString);Prior to this detect-browser would try and be smart enough to work out where to look, but if you were using it in cases where you wanted to parse a useragent string that you had received from a HTTP header or the like it definitely would not have worked, this change (thanks to @rshtg - see #114) fixes that.