thillmann/bowser-jr

A lightweight browser detector utility

Bowser Jr.

A small, lightweight and composable browser detection utility heavily inspired by bowser.

Installation

Install it using your favourite package manager:

$ npm install bowser-jr
# or
$ yarn add bowser-jr
# or
$ pnpm add bowser-jr

Usage

Now just import getParser and the parsers you need:

import { getParser } from 'bowser-jr';
import { getBrowserName, browserParser } from 'bowser-jr/browser';

const parser = getParser(window.navigator.userAgent, { use: [browserParser] });

console.log(getBrowserName(parser)); // outputs `Firefox`

Using multiple parsers

You can use multiple parsers to extract more information from the user agent:

import { getParser } from 'bowser-jr';
import { browserParser } from 'bowser-jr/browser';
import { engineParser } from 'bowser-jr/engine';
import { osParser } from 'bowser-jr/os';
import { platformParser } from 'bowser-jr/platform';

const parser = getParser(window.navigator.userAgent, {
    use: [browserParser, engineParser, osParser, platformParser],
});

console.log(parser.getResult());

Bowser compat utilities

bowser-jr also comes with a compatibility utility for bowser to make adoption a little easier:

import BowserCompat from 'bowser-jr/compat';

const browser = BowserCompat.getParser(window.navigator.userAgent);
console.log(browser.getBrowser());

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

bowser-jr's Issues

Error: Package subpath './browser' is not defined by "exports"

I tried creating a middleware using bowser-jr but I couldn't compile for some reason.

Error importing 'bowser-jr/compat' in ESM project

Hi @thillmann,

I would kindly ask if it would be possible to fix the issue I was stumbling upon using the module with ESM?

The issue was when importing 'bowser-jr/compat' in my ESM project.
I was getting the error:

Error: Package subpath './compat' is not defined by "exports" in <projectpath>\node_modules\bowser-jr\package.json imported from <file that import the 'bowser-jr/compat'>
     at new NodeError (node:internal/errors:387:5)
     at throwExportsNotFound (node:internal/modules/esm/resolve:365:9)
     at packageExportsResolve (node:internal/modules/esm/resolve:649:3)
     at packageResolve (node:internal/modules/esm/resolve:833:14)
     at moduleResolve (node:internal/modules/esm/resolve:901:20)
     at defaultResolve (node:internal/modules/esm/resolve:1115:11)
     at nextResolve (node:internal/modules/esm/loader:163:28)
     at ESMLoader.resolve (node:internal/modules/esm/loader:841:30)
     at ESMLoader.getModuleJob (node:internal/modules/esm/loader:424:18)
     at ModuleWrap.<anonymous> (node:internal/modules/esm/module_job:76:40)

I added a pull request regarding that: #2

Would you like to accept that?
If corrections, changes or adjustments are needed don't hesitate to reply.

kind regards