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

ember-window

v1.0.5

Published

The default blueprint for ember-cli addons.

Downloads

17

Readme

Ember-window

This service exists as a layer on top of the javascript window Object, to be able to mock it easily in tests (without mocking this service in tests, the https://localhost:4200/tests page would be redirected when using window.location.href=xxx in our code). It may also be useful if we want to run the app outside a browser at some point . In this service we can get and set the properties applied to the window Object, so this allows observing them / adding CPs if ever needed.

Usage is the same as for the javascript window Object:

instead of:

window.location.href = '/Your_Account/Account_Details/';

use:

window: Ember.inject.service(),
..
this.get('window.location').href = '/Your_Account/Account_Details/';

In your tests, you can use something like:

// tests/helpers/start-app.js
export default function startApp(attrs) {
  let application;

  let attributes = Ember.merge({}, config.APP);
  attributes = Ember.merge(attributes, attrs); // use defaults, but you can override;

  Ember.run(() => {
    let windowService;

    application = Application.create(attributes);
    windowService = application.resolveRegistration('service:window');

    // Mock the window service
    windowService.reopen({
      windowObject: {
        location: {
          pathname: 'my-account',
          href: null
        }
      }
    });

    application.setupForTesting();
    application.injectTestHelpers();
  });

  return application;
}