Security News
JavaScript Leaders Demand Oracle Release the JavaScript Trademark
In an open letter, JavaScript community leaders urge Oracle to give up the JavaScript trademark, arguing that it has been effectively abandoned through nonuse.
The bowser npm package is a browser detection library. It helps in identifying the browser and rendering engine a user is using, as well as providing information about the browser's capabilities, such as whether it supports touch events or service workers. This can be particularly useful for tailoring user experiences to different environments or for analytics and debugging purposes.
Browser Detection
Detects the browser name using the user agent string.
const Bowser = require('bowser');
const browser = Bowser.getParser(window.navigator.userAgent);
const browserName = browser.getBrowserName();
Browser Version Detection
Determines the version of the browser being used.
const Bowser = require('bowser');
const browser = Bowser.getParser(window.navigator.userAgent);
const browserVersion = browser.getBrowserVersion();
Platform Detection
Identifies the platform (desktop, mobile, tablet, etc.) on which the browser is running.
const Bowser = require('bowser');
const browser = Bowser.getParser(window.navigator.userAgent);
const platformType = browser.getPlatformType();
Feature Checks
Checks if the browser supports certain features, such as touch events.
const Bowser = require('bowser');
const browser = Bowser.getParser(window.navigator.userAgent);
const supportsTouch = browser.satisfies({
'mobile': { 'touch': true }
});
OS Detection
Determines the operating system on which the browser is running.
const Bowser = require('bowser');
const browser = Bowser.getParser(window.navigator.userAgent);
const osName = browser.getOSName();
The 'useragent' package is similar to 'bowser' in that it parses user agent strings to detect browser information. However, it focuses more on the parsing aspect and less on the browser's capabilities.
The 'platform' package provides information about the operating system, browser, and device based on the user agent string. It is similar to 'bowser' but has a simpler API and less detailed detection of browser features.
The 'detect-browser' package is another alternative for detecting browser information from the user agent string. It is a smaller and more lightweight library compared to 'bowser', but it may not offer as comprehensive feature detection.
A Browser detector. Because sometimes, there is no other way, and not even good modern browsers always provide good feature detection mechanisms.
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 the 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.
First of all, require the library:
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:
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"
}
}
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.getParsers(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"
});
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.
By default, require('bowser')
requires the pre-compiled file, which can
include useless for you polyfills. In case you don't need that, you can choose
using source file requiring bowser like that: require('bowser/src/bowser
);
Then you get ES2015 file, which is not precompiled and can be easier to debug.
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
$ npm test
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.
Licensed as MIT. All rights not explicitly granted in the MIT license are reserved. See the included LICENSE file for more details.
2.0.0-alpha.1 (July 9, 2018)
Bowser.getParser()
Bowser.parse
Parser
class which describes parsing processFAQs
Lightweight browser detector
The npm package bowser receives a total of 10,030,641 weekly downloads. As such, bowser popularity was classified as popular.
We found that bowser demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
In an open letter, JavaScript community leaders urge Oracle to give up the JavaScript trademark, arguing that it has been effectively abandoned through nonuse.
Security News
The initial version of the Socket Python SDK is now on PyPI, enabling developers to more easily interact with the Socket REST API in Python projects.
Security News
Floating dependency ranges in npm can introduce instability and security risks into your project by allowing unverified or incompatible versions to be installed automatically, leading to unpredictable behavior and potential conflicts.