npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@baloise/web-app-unsupported-browsers

v3.14.0

Published

Utilities for Baloise Web Applications

Downloads

61

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

assistentenitchassistentenitchmadalina.iacobmadalina.iacobyannickholzenkampyannickholzenkampmontakasparsonemontakasparsoneteam_mortalteam_mortalmladenplaninicicmladenplaninicicnobilonobilothomasseyssenstpothomasseyssenstpose-aperto-comse-aperto-combaopsobaopsohirsch88hirsch88

Keywords

Readme

@baloise/web-app-unsupported-browsers

Continuous Release npm npm bundle size npm GitHub GitHub issues

This script verifies if the users browser is supported by the Baloise applications and if not it redirects directly to the static unsupported-browsers pages.

Installation

Fist we install the javascript package with npm.

npm install @baloise/web-app-unsupported-browsers

The javascript file needs to be served as a static file therefore use the package copyfiles


npm install copyfiles --save-dev

After installing our copyfiles dependency we need to define the copy command in our package.json file. Add a new script called copy:script and adjust the second path to your application.

Then we add the defined script copy:script in our postinstall script. Every time we install dependencies the copy:fonts script gets executed at the end.

"scripts": {
  "postinstall": "npm run copy:script",
  "copy:script": "copyfiles --flat node_modules/@baloise/web-app-unsupported-browsers/dist/* public/assets/js"
}

Lets add the script to the head of the entry html page.

<head>
  ...
  <script
    src="public/assets/js/baloise-unsupported-browsers.js"
    data-location="ch"
  ></script>
</head>

Attributes

The script supports two attributes:

  • data-location
    • default is ch
    • possible values are ch,be,lu and de
  • data-language
    • default is browser-language if supported and if not then the default of the location
      • ch would be de
      • be would be fr
      • lu would be fr
      • de would be de