1
0
mirror of https://github.com/lancedikson/bowser synced 2024-10-27 20:34:22 +00:00
Go to file
dependabot[bot] efd9bca055
chore(deps): bump loader-utils from 1.2.3 to 1.4.2
Bumps [loader-utils](https://github.com/webpack/loader-utils) from 1.2.3 to 1.4.2.
- [Release notes](https://github.com/webpack/loader-utils/releases)
- [Changelog](https://github.com/webpack/loader-utils/blob/v1.4.2/CHANGELOG.md)
- [Commits](https://github.com/webpack/loader-utils/compare/v1.2.3...v1.4.2)

---
updated-dependencies:
- dependency-name: loader-utils
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>
2022-11-18 12:19:32 +00:00
.github fix(chore): bug with babel/helper-compilation on build 2020-07-09 21:27:15 +03:00
docs chore: bump version, write changelog and docs 2020-09-12 11:22:31 +03:00
src Merge pull request #427 from YongliangDing/declaration-update 2020-09-12 10:35:50 +03:00
test Merge pull request #437 from willamesoares/include-alias-check 2020-09-12 10:25:35 +03:00
.babelrc fix(babelrc): fix bundling from auto modules to cjs 2019-07-17 16:47:44 +03: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 Make prefer-default-export rule warning 2019-04-18 21:33:45 +03:00
.gitignore chore(gitignore): ignore .gz files 2019-07-17 13:47:55 +03:00
.npmignore Exclude unnecessary files from the npm package 2020-02-25 16:58:43 +01: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 chore(travis): fix node_js version 2020-06-01 23:44:54 +03:00
CHANGELOG.md chore: bump version, write changelog and docs 2020-09-12 11:22:31 +03:00
index.d.ts Add missing typescript property declaration 2020-09-12 10:39:01 +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 chore(deps): bump loader-utils from 1.2.3 to 1.4.2 2022-11-18 12:19:32 +00:00
package.json chore: bump version, write changelog and docs 2020-09-12 11:22:31 +03:00
README.md Add bowser-online to README.md 2020-06-01 23:39:46 +03:00
webpack.config.js chore(deps): adds compression-webpack-plugin 2019-07-17 13:47:55 +03:00

Bowser

A small, fast and rich-API browser/platform/engine detector for both browser and node.

  • Small. Use plain ES5-version which is ~4.8kB gzipped.
  • Optimized. Use only those parsers you need — it doesn't do useless work.
  • Multi-platform. It's browser- and node-ready, so you can use it in any environment.

Don't hesitate to support the project on Github or OpenCollective if you like it ❤️ Also, contributors are always welcome!

Financial Contributors on Open Collective Build Status Greenkeeper badge Coverage Status Downloads

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. Check it out on this page: https://bowser-js.github.io/bowser-online/.

⚠️ Version 2.0 breaking changes ⚠️

Version 2.0 has drastically changed the API. All available methods are on the docs page.

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 browser = Bowser.getParser(window.navigator.userAgent);
console.log(browser.getBrowser());

// outputs
{
  name: "Internet Explorer"
  version: "11.0"
}

or

console.log(Bowser.parse(window.navigator.userAgent));

// 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.

Browser names for .satisfies()

By default you are supposed to use the full browser name for .satisfies. But, there's a short way to define a browser using short aliases. The full list of aliases can be found in the file.

Similar Projects

  • Kong - A C# port of Bowser.

Contributors

Code Contributors

This project exists thanks to all the people who contribute. [Contribute].

Financial Contributors

Become a financial contributor and help us sustain our community. [Contribute]

Individuals

Organizations

Support this project with your organization. Your logo will show up here with a link to your website. [Contribute]

License

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