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

@nimiq/browser-warning

v1.1.1

Published

Browser Warning for unsupported browsers

Downloads

126

Readme

Nimiq Browser Warnings

Javascipt, CSS and a html snippet to display a warning in case of unsupported browsers, private mode or disabled Javascript.

Installation

yarn add @nimiq/browser-warning

Usage

This is no modular package you can import. Instead:

  • Use e.g. CopyWebpackPlugin to copy files from dist folder to your app's root folder
  • Use e.g. HtmlWebpackPlugin to inject the HTML snippet into your app's index.html
  • In your index.html head section, place <script type="text/javascript" src="browser-warning.js" defer></script> in front of all other scripts which may execute, especially your app's main entry point. If your other scripts are not deferred, also remove the defer attribute on browser-warning.js.
  • In your app's main entry point logic, check for window.hasBrowserWarning === true and stop execution in that case.
  • If you're using typescript, add @nimiq/browser-warning to compilerOptions.types in your tsconfig.json.
  • It is recommended to serve your app via https as otherwise in-app web-views might not be correctly detected.

Configuration

You can define a callback window.onBrowserWarning that gets called in case of a browser warning with the warning type and a config object:

|Parameter|Type| |---------|----| |warningType|'web-view' / 'browser-outdated' / 'no-local-storage' / 'private-mode'| |warningConfig.headline|string| |warningConfig.message|string| |warningConfig.hasShareButton|boolean| |warningConfig.shareUrl|string| |warningConfig.useNativeShare|boolean| |warningConfig.shareInstructions|string|

It can then optionally return a configuration object that overwrites a subset or all of the configuration properties.

Note that window.onBrowserWarning needs to be defined before browser-warning.js is executed. This is therefore an exception to the rule stated in the previous section.

Note that the script that defines window.onBrowserWarning must be written in old-fashioned Javascript to not fail with syntax errors in old browsers which would prevent us from being able to display a warning in old browsers.

Contributing

Contributions are welcome! To build the code yourself run

yarn build

which minifies the code with Google's closure compiler. We are compiling with the compiler's SIMPLE compilation level as the ADVANCED level does not result in significantly smaller files for this lib, especially when comparing gzipped size. You therefore do not need to mind the special precautions that are required for the ADVANCED level.

Code does however need to be written in old-fashioned javascript to be compatible with old browsers. The closure compiler will warn you if your code is not valid ES3.