@ -22,7 +22,7 @@ The upcoming 2.0 version has drastically changed API. All available methods can
First of all, require the library:
First of all, require the library:
```
```javascript
const bowser = require('bowser');
const bowser = require('bowser');
```
```
@ -30,7 +30,7 @@ const bowser = require('bowser');
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 make it with Bowser:
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 make it with Bowser:
```
```javascript
const browser = bowser.getParser(window.navigator.userAgent);
const browser = bowser.getParser(window.navigator.userAgent);
console.log(`The current browser name is "${browser.getBrowserName()}"`);
console.log(`The current browser name is "${browser.getBrowserName()}"`);
@ -39,7 +39,7 @@ console.log(`The current browser name is "${browser.getBrowserName()}"`);
or
or
```
```javascript
const impression = new Impression();
const impression = new Impression();
const browser = bowser.getParser(window.navigator.userAgent);
const browser = bowser.getParser(window.navigator.userAgent);
@ -50,7 +50,7 @@ impression.brVer = browserInfo.version;
or
or
```
```javascript
const browser = bowser.getParser(window.navigator.userAgent);
const browser = bowser.getParser(window.navigator.userAgent);
impression.userTechData = browser.parse();
impression.userTechData = browser.parse();
console.log(impression.userTechData);
console.log(impression.userTechData);
@ -81,7 +81,7 @@ console.log(impression.userTechData);
You could want to filter some particular browsers to provide any special support for them or make any workarounds.
You could want to filter some particular browsers to provide any special support for them or make any workarounds.
It could look like this:
It could look like this:
```
```javascript
const browser = bowser.getParsers(window.navigator.userAgent);
const browser = bowser.getParsers(window.navigator.userAgent);
const isValidBrowser = browser.satisfies({
const isValidBrowser = browser.satisfies({
// declare browsers per OS
// declare browsers per OS
@ -111,10 +111,11 @@ Thus, you can define OS or platform specific rules and they will have more prior
More of API and possibilities you will find in the `docs` folder.
More of API and possibilities you will find in the `docs` folder.
# Advanced Usage
# Advanced Usage
By default, `require('bowser')` requires the pre-compiled file, which can
By default, `require('bowser')` requires the *ES6 version of files* , which
include useless for you polyfills. In case you don't need that, you can choose
**don't** include any polyfills. In case if you don't use your own `babel-polyfill`
using source file requiring bowser like that: `require('bowser/src/bowser` );
you may need to have pre-built bundle with all needed polyfills.
Then you get ES2015 file, which is not precompiled and can be easier to debug.
It's possible requiring bowser like that: `require('bowser/compiled');`
As result you get a ES5 file with `babel-polyfill` bundled in it.
# Contributing
# 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):
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):
Denis Demchenko
6 years ago