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

@aleen42/karma-ie-launcher

v1.0.2

Published

A Karma plugin. Launcher for Internet Explorer.

Downloads

5

Readme

karma-ie-launcher

js-standard-style npm version npm downloads

Build Status Dependency Status devDependency Status

Launcher for Internet Explorer.

Installation

The easiest way is to keep karma-ie-launcher as a devDependency, by running

npm install karma-ie-launcher --save-dev

Configuration

// karma.conf.js
module.exports = function(config) {
  config.set({
    browsers: ['IE']
  });
};

You can pass list of browsers as a CLI argument too:

karma start --browsers IE

You can run IE in emulation mode by setting the 'x-ua-compatible' option:

customLaunchers: {
  IE9: {
    base: 'IE',
    'x-ua-compatible': 'IE=EmulateIE9'
  },
  IE8: {
    base: 'IE',
    'x-ua-compatible': 'IE=EmulateIE8'
  }
}

See Specifying legacy document modes on MSDN.

Running IE in "No add-ons mode"

Please note that since v0.2.0 default behaviour of launching Internet Explorer has changed. Now it runs using system-wide configuration (uses same settings as if you would run it manually) but prior to v0.2.0 it was spawned with -extoff flag set explicitly, so all extensions were disabled.

If you expect the same behaviour as it was before v0.2.0, Karma configuration should be slightly changed:

  • create new customLauncher configuration (IE_no_addons is used in an example below) with custom flags (in our case it is -extoff only)
  • browser IE in browsers field should be replaced with your new custom launcher name
  browsers: ['IE_no_addons'],
  customLaunchers: {
    IE_no_addons: {
      base:  'IE',
      flags: ['-extoff']
    }
  }

See IE Command-Line Options on MSDN.


For more information on Karma see the homepage.