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

@onyourmarks/outdated-browser-rework

v3.0.0

Published

Detects outdated browsers and asks users to upgrade to a new version. Handles mobile devices!

Downloads

32

Readme

Outdated Browser Rework

Detects outdated browsers and advises users to upgrade to a new version. Handles mobile devices!

This is a fork of Burocratik's Outdated Browser, adding a number of new features including:

  • Explicit browser version support
  • Mobile browser support
  • Edge support
  • Substantial size reduction
  • More translations
  • Custom upgrade messages
  • Unminified code
  • Removed adware (Burocratik sold their site to a VPN company)

And more (see below for the full list).

One of the challenges with making this type of module is that the JS and CSS can't use any current tech - the 'get a new browser' message must display on older browsers - so yes, this is hard. We have to use ES3, an ancient version of JavaScript. We can't even use the nice '×' close character (we have to use the letter 'x') since that character doesn't display on some older browsers! This module is tested all the way back to IE6.

This module does not need jQuery.

Demo

Outdated Browser Rework was created by, for, and is used in production at, EV HTTPS provider CertSimple. You can see it working there.

If you want to force your browser to be unsupported, you can also check out a demo where all browsers are unsupported.

Usage (with browserify)

JS

In your template

In <head>, before any other script tags:

<script src="/js/dist/oldbrowser.js"></script>

In oldbrowser.js

Start outdated-browser-rework and call it with your preferred options:

var outdatedBrowserRework = require("outdated-browser-rework");
outdatedBrowserRework();

If you like, specify options, eg:

outdatedBrowserRework({
	browserSupport: {
		Chrome: 57, // Includes Chrome for mobile devices
		Edge: 39,
		Safari: 10,
		"Mobile Safari": 10,
		Firefox: 50,
		Opera: 50,
		Vivaldi: 1,
		// You could specify minor version too for those browsers that need it.
		Yandex: { major: 17, minor: 10 },
		// You could specify a version here if you still support IE in 2017.
		// You could also instead seriously consider what you're doing with your time and budget
		IE: false
	},
	requireChromeOnAndroid: false,
	isUnknownBrowserOK: false,
	messages: {
		en: {
			outOfDate: "Your browser is out of date!",
			unsupported: "Your browser is not supported!",
			update: {
				web: "Update your browser to view this website correctly. ",
				googlePlay: "Please install Chrome from Google Play",
				appStore: "Please update iOS from the Settings App"
			},
			// You can set the URL to null if you do not want a clickable link or provide
			// your own markup in the `update.web` message.
			url: "http://outdatedbrowser.com/",
			callToAction: "Update my browser now",
			close: "Close"
		}
	}
});

The particular versions used in this example are the defaults, by the way!

See below for more options.

Browsers that are older than the versions supplied, or who use a browser where support is false, will see a message, depending on their platform:

  • On desktop browsers, users will be directed to outdatedbrowser.com
  • on iOS devices, users will be asked to visit the Settings app and upgrade their OS.
  • On Android devices, users will be directed to Chrome in Google Play.

Usage (without browserify)

In your template

In <head>, before any other script tags:

<script src="/js/dist/outdated-browser-rework.min.js"></script>
<script>
	outdatedBrowserRework();
</script>

See above for the default options.

Options

  • browserSupport: Object - A matrix of browsers and their versions - see above for demo. Anything less will be unsupported. false means all versions are unsupported.
  • requiredCssProperty: String - A CSS property that must be supported.
  • messages: Object - Customize upgrade messages for your purposes. See the above default options for an example.
  • language: String - A language string to be used for the messages in the notification. Default is en. See languages.json for supported languages. Can be used instead of messages if preferred.
  • requireChromeOnAndroid: Boolean - Ask Android users to install Chrome. Default is false.
  • isUnknownBrowserOK: Boolean. Whether unknown browsers are considered to be out of date or not. The default is false, ie. unknown browsers are considered to be out of date. Consider setting true and using requiredCssProperty to catch missing features.

SCSS

If you're using sass-npm you can just import the npm module, and it will load index.scss:

@import "outdated-browser-rework.scss";

Otherwise compile the sass and put it somewhere. Then load that via a link tag inside <head>:

<link rel="stylesheet" href="/css/outdated-browser.css" />

HTML

Add the required HTML at the end of your document:

<div id="outdated"></div>

Yes, IDs suck but old browsers don't support gettting elements by class name.

You should also always use HTML declaration to tell legacy browsers that you're using full standards mode. Without this it's possible that your page gets loaded in the quirks mode and it will not work with this package.
For more information, see: https://developer.mozilla.org/en-US/docs/Web/HTML/Quirks_Mode_and_Standards_Mode

Bundling the JavaScript

In modern times we normally concatenate and combine different JS modules using browserify or webpack: it's best to bundle outdated-browser-rework by itself. Since other scripts may expect things like console and function.bind() to exist, they won't work on old browsers - if you bundle this with other software, the JS will probably fail before outdated-browser has a chance to do any work.

For gulp users

Add the following underneath your existing js task:

gulp
	.src("./public/js/src/oldbrowser.js")
	.pipe(
		browserify({
			debug: !gulp.env.production
		})
	)
	.pipe(gulp.dest("./public/js/dist"));

Doing this will mean that dist/oldbrowser.js will only include outdated-browser-rework and its dependency user-agent-parser, without anything else to get in the way.

For Webpack users

First of all, to bundle outdated-browser-rework by itself, create a new entry point in your webpack config file. You'll also need to install style-loader and css-loader in order to import the package's CSS. Your webpack configuration should look something like this:

const path = require("path");

module.exports = {
	entry: {
		main: path.join(__dirname, "src/index.js"),
		"outdated-browser-rework": path.join(
			__dirname,
			"src/outdated-browser-rework.js"
		)
	},
	module: {
		rules: [
			{
				test: /\.css$/i,
				use: ["style-loader", "css-loader"]
			}
		]
	}
};

Secondly, make use of outdated-browser-rework in src/outdated-browser-rework.js:

import outdatedBrowser from "outdated-browser-rework";
import "outdated-browser-rework/dist/style.css";

outdatedBrowser();

Finally, add the generated JS file in your HTML:

<!DOCTYPE html>
<html>
	<head>
		<title>Webpack example</title>
	</head>
	<body>
		<div id="outdated"></div>
		<script src="outdated-browser-rework.js"></script>
		<script src="main.js"></script>
	</body>
</html>

Outdated Browser Rework Version 2 notes

  • Add isUnknownBrowserOK option to determine how to handle unknown browsers.
  • Add messages to override the default out of date messages.
  • Custom message for unsupported browsers vs out of date versions of browsers
  • Edge versions are now specified directly (rather than using EdgeHTML versions). For example, you now specify Edge 16 rather than 41.
  • Better documentation
  • New translations
  • Custom upgrade messages
  • New false option to disable browser support.
  • IE now defaults to false - ie, display a message telling users to get a new browser on any version of IE. You can still specify 6 to 11 if, for some reason, you still support IE in 2018. Tip: you should not support IE in 2018.
  • CSS file is included
  • Update ua-parser-js to fix parsing some more esoteric UAs

Differences from Bürocratik's Outdated Browser 1.1.0

  • Add explicit browser support via the browserSupport option
  • Add mobile support. Users on iOS and Android will be directed to the Apple App Store and Google Play respectively.
  • Add new requireChromeOnAndroid option
  • Be an NPM module
  • Use SASS (specifically SCSS)
  • No AJAX, languages are only 8K and removing the AJAX library has made the code substantially shorter.
  • Added support for custom upgrade messages

And some code fixes:

  • Pass eslint
  • vanilla JS (no jQuery!)
  • Simplify some variable and function names

There's still some TODOs from the original code:

  • Try and eliminate IDs (they're JS globals, so EUW)
  • Move all styling into SCSS (need to test if this breaks old IEs)
  • Re-do Farsi (RTL) support from original Outdated Browser

Author

This rework is made by Mike MacCana and a whole bunch of amazing open source contributors!

The original Outdated Browser is made with love at Bürocratik

Changes in thes fork by TDE

  • Store close-click in LocalStorage (when it's available). The user can use the website in their old browser without the message (for one week);
  • Add new option in languages; global message. Between update message and title;
  • Remove other languages than EN and NL;
  • Remove opacity and transition of message. Show it directly;