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-devtools

v6.0.0

Published

A collection of useful functions for developing Ember apps

Downloads

864

Readme

ember-devtools

Visit project page and demo

A collection of useful functions for developing Ember apps. Best served from the console.

Usage

ember-devtools is an Ember.Service that is most useful when available in the devtools console. The simplest was access this from the console is using a global variable (eww!) which can be defined in config/environment.js.

var ENV = {
  'ember-devtools': {
    global: true,
    enabled: environment === 'development'
  }
}

Setting global will allow access to the devTools functions globally (eg. you can run routes() in the console). If you'd prefer these functions to be under a prefix set global: 'devTools' for devTools.routes().

The enabled option will enable the addon. By default, this addon will only be included in the development environment.

Alternatively you can use Ember.inject.service('ember-devtools') or appInstance.lookup('service:ember-devtools').

Functions

app([name])

Returns the named application. name defaults to main.

routes()

Returns the names of all routes.

route([name])

Returns the named route. name defaults to the current route.

router([name])

Returns the named router instance. name defaults to main.

model([name])

Returns the model for the named controller. name defaults to the the current route.

service(name)

Performs a lookup for the named service in the owner (using 'service:' + name).

controller([name])

Returns the named controller. name defaults to the current route.

log(promise[, property[, getEach]])

Resolves the promise and logs the resolved value using console.log. Also sets window.$E to the resolved value so you can access it in the dev tools console.

If property is specified then $E.get(property) will be logged.

If getEach is true then $E.getEach(property) will be logged.

Examples:

> log(store.find('organisation')) => undefined
> $E.get('length') => 3
> log(store.find('organisation'), 'length') => 3
> log(store.find('organisation'), 'name', true) => array of names

lookup(name)

Performs a lookup for the named entry in the owner, which will in turn ask its resolver if it's not found.

resolveRegistration(name)

Performs a lookup for the named factory in the registry.

ownerNameFor(obj)

Searches the owner to find the name for the specified object (if any).

inspect

Does what it says, in a manner of speaking. Alias to Ember.inspect.

logResolver(bool = true)

Switch logging for the resolver on or off.

logAll(bool = true)

Switch logging for all the things on/off.

logRenders()

Logs the rendering duration (in milliseconds) of each component, view and helper.

globalize()

Attach all of these useful functions to the window object (eww!) - useful for accessing in the console.

getOwner(obj = this)

The owner of the service or specified obj.

config()

Returns the Application config

Properties

owner

The owner of the service. n.b. this is not globalised (to avoid conflict with window.owner), use getOwner() instead.

store

The Ember Data Store.

typeMaps

The Ember Data 'type map'.

Installation

Ember CLI

npm install ember-devtools --save-dev

Upgrading From v2.0

ember-devtools is now dependent on ember-cli.

Changelog

  • v6: container and containerNameFor are now owner and ownerNameFor