You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Go to file
Denis Demchenko b2d641e647
Fix nyc config to exclude built files from coverage
5 years ago
docs Improve documentation language, fix an example 6 years ago
src Added support for Googlebot recognition 5 years ago
test Added support for Googlebot recognition 5 years ago
.babelrc Avoid babel debug during building 6 years ago
.coveralls.yml Add coveralls.yml 6 years ago
.editorconfig Fix failing tests 5 years ago
.eslintrc.yml Fix travis testing (include eslint) 6 years ago
.gitignore Compile 2 versions of files (es5 and bundled) 6 years ago
.npmignore Fix dotfiles 6 years ago
.npmrc Add .npmrc 6 years ago
.nycrc Fix nyc config to exclude built files from coverage 5 years ago
.testem.json Add testem as a main test runner 7 years ago
.travis.yml Update .travis.yml 5 years ago
CHANGELOG.md Bump version, write changelog 6 years ago
CONTRIBUTING.md Add contributing.md 6 years ago
ISSUE_TEMPLATE.md Fix templates and repo meta information 6 years ago
LICENSE adds license 9 years ago
README.md Updated Readme upon the changes to typings 5 years ago
index.d.ts Added a definitive-working definition for v2 5 years ago
jsdoc.json Rebuild documentation 6 years ago
package-lock.json Improve documentation language, fix an example 6 years ago
package.json Update package.json 5 years ago
webpack.config.js Compile 2 versions of files (es5 and bundled) 6 years ago

README.md

Bowser

A browser detector. Because sometimes, there is no other way, and not even good modern browsers always provide good feature detection mechanisms.

Build Status Greenkeeper badge

Contents

Overview

The library is made to help to detect what browser your user has and gives you a convenient API to filter the users somehow depending on their browsers.

Please, note that this is an alpha version. Check out the 1.x branch for a stable version.

Changes of version 2.0 The upcoming 2.0 version has drastically changed API. All available methods can be found in the docs folder from now on and on a webpage soon.

Use cases

First of all, require the library. This is a UMD Module, so it will work for AMD, Typescript and CommonJS module systems.

const Bowser = require("bowser"); // CommonJS

import * as Bowser from "bowser" // Typescript

By default, the exported version is the ES5 transpiled version, which do not include any polyfills.

In case you don't use your own babel-polyfill you may need to have pre-built bundle with all needed polyfills. So, for you it's suitable to require bowser like this: require('bowser/bundled'). As the result, you get a ES5 version of bowser with babel-polyfill bundled together.

You may need to use the source files, so they will be available in the package as well.

Browser props detection

Often we need to pick users' browser properties such as the name, the version, the rendering engine and so on. Here is an example how to do it with Bowser:

const browser = bowser.getParser(window.navigator.userAgent);

console.log(`The current browser name is "${browser.getBrowserName()}"`);
// The current browser name is "Internet Explorer"

or

const impression = new Impression();

const browser = bowser.getParser(window.navigator.userAgent);
const browserInfo = browser.getBrowser();
impression.brName = browserInfo.name;
impression.brVer = browserInfo.version;

or

const browser = bowser.getParser(window.navigator.userAgent);
impression.userTechData = browser.parse();
console.log(impression.userTechData);

// outputs
{
  browser: {
    name: "Internet Explorer"
    version: "11.0"
  },
  os: {
    name: "Windows"
    version: "NT 6.3"
    versionName: "8.1"
  },
  platform: {
    type: "desktop"
  },
  engine: {
    name: "Trident"
    version: "7.0"
  }
}

Filtering browsers

You could want to filter some particular browsers to provide any special support for them or make any workarounds. It could look like this:

const browser = bowser.getParser(window.navigator.userAgent);
const isValidBrowser = browser.satisfies({
  // declare browsers per OS
  windows: {
    "internet explorer": ">10",
  },
  macos: {
    safari: ">10.1"
  },

  // per platform (mobile, desktop or tablet)
  mobile: {
    safari: '>9',
    'android browser': '>3.10'
  },

  // or in general
  chrome: ">20.1.1432",
  firefox: ">31",
  opera: ">22"
  
  // also supports equality operator
  chrome: "=20.1.1432", // will match particular build only

  // and loose-equality operator
  chrome: "~20"         // will match any 20.* sub-version
  chrome: "~20.1"       // will match any 20.1.* sub-version (20.1.19 as well as 20.1.12.42-alpha.1)
});

Settings for any particular OS or platform has more priority and redefines settings of standalone browsers. Thus, you can define OS or platform specific rules and they will have more priority in the end.

More of API and possibilities you will find in the docs folder.

Contributing

If you'd like to contribute a change to bowser, modify the files in src/, then run the following (you'll need node + npm installed):

$ npm install #build
$ npm test #run tests
$ npm run lint #check lint rules

Adding tests

See the list in test/acceptance/useragentstrings.yml with example user agents and their expected bowser object.

Whenever you add support for new browsers or notice a bug / mismatch, please update the list and check if all tests are still passing.

Similar Projects

  • Kong - A C# port of Bowser.

License

Licensed as MIT. All rights not explicitly granted in the MIT license are reserved. See the included LICENSE file for more details.