npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

uainfer

v0.5.0

Published

Infer UA from its UA String

Downloads

1,660

Readme

uainfer

NPM version Build Status

This is a simple JavaScript library (MIT License) to infer the user agent from its claimed User-Agent string. The objective of uainfer to provide a human-friendly answer to the inquiry "What browser am I using?".

In the context of a web browser, the most common way to obtain the User-Agent string is from the value of navigator.userAgent. In the context of an HTTP server, it can be retrieved from the User-Agent header field in the HTTP request.

Example usage with Node.js REPL (or try it on RunKit):

> uainfer = require('uainfer');
> ua = uainfer.analyze('Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.2)'
> ua.toString()
'Internet Explorer 7 on Windows XP'

(To use this library in a front-end application, see this JSFiddle demo)

For browsers utilizing Chrome/Blink engine (Samsung Browser, Opera, Vivaldi, etc), the result can contain the corresponding equivalent version of Chrome:

> console.log(ua)
UserAgent {
  browser:
   { name: 'Vivaldi',
     version: 1.96,
     fullVersion: '1.96.1147.52',
     chromeFamily: { version: 65, fullVersion: '65.0.3325.183' } },
  os: { name: 'Windows', version: '10' } }

Non-goals:

  • Recognize every single web browsers and obscure user agents out there.
  • Deduce other information such as CPU type, device, form factor, etc.

Design choices:

  • For a better maintenance, avoid regular expressions.
  • Always expand its small but fairly extensive test suite.
  • Keep it tidy and lightweight (4 KB when minified).

This library is created and maintained by @AriyaHidayat.