1
0
mirror of https://github.com/lancedikson/bowser synced 2024-10-27 20:34:22 +00:00
Go to file
2019-02-05 04:09:51 +00:00
docs Fix the docs 2019-01-19 15:44:08 +02:00
src Merge pull request #288 from ffaubert/add-engine-api 2019-01-24 22:44:29 +02:00
test Merge pull request #288 from ffaubert/add-engine-api 2019-01-24 22:44:29 +02:00
.babelrc chore(package): update lockfile package-lock.json 2019-01-19 12:46:51 +02:00
.coveralls.yml Add coveralls.yml 2018-06-30 17:29:34 +03:00
.editorconfig Fix failing tests 2019-01-07 00:23:01 +02:00
.eslintrc.yml Fix travis testing (include eslint) 2018-09-09 13:25:07 +03:00
.gitignore Compile 2 versions of files (es5 and bundled) 2018-07-22 19:31:49 +03:00
.npmignore Fix dotfiles 2018-07-09 21:48:04 +03:00
.npmrc Add .npmrc 2018-07-17 21:10:09 +03:00
.nycrc Fix nyc config to exclude built files from coverage 2019-01-19 11:49:28 +02:00
.testem.json Add testem as a main test runner 2017-06-08 22:23:27 +03:00
.travis.yml Update .travis.yml 2019-01-10 00:34:21 +01:00
CHANGELOG.md Bump version, write changelog 2019-01-24 23:06:07 +02:00
CONTRIBUTING.md Improve CONTRIBUTING.md 2019-01-21 14:22:44 -08:00
index.d.ts Fixed broken indentation for typings 2019-01-19 16:42:58 +01:00
ISSUE_TEMPLATE.md Fix templates and repo meta information 2018-07-05 10:07:22 +03:00
jsdoc.json Rebuild documentation 2018-07-08 12:09:27 +03:00
LICENSE adds license 2015-07-25 18:56:12 -07:00
package-lock.json Bump version, write changelog 2019-01-24 23:06:07 +02:00
package.json chore(package): update nyc to version 13.2.0 2019-02-05 04:09:51 +00:00
README.md Merge pull request #284 from JBallin/readme-import-instructions 2019-01-22 21:07:07 +02:00
webpack.config.js chore(package): update lockfile package-lock.json 2019-01-19 12:46:51 +02:00

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 badgeCoverage Status

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.

Changes of version 2.0

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

For legacy code, check out the 1.x branch and install it through npm install bowser@1.9.4.

Use cases

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

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

import * as Bowser from "bowser"; // TypeScript

import Bowser from "bowser"; // ES6 (and TypeScript with --esModuleInterop enabled)

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.

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.