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

v2.10.0

Published

[![Sauce Test Status](https://saucelabs.com/browser-matrix/ember-ci.svg)](https://saucelabs.com/u/ember-ci)

Downloads

4

Readme

Ember.js Build Status Code Climate Slack

Sauce Test Status

Ember.js is a Javascript framework that greatly reduces the time, effort and resources needed to build any web application. It is focused on making you, the developer, as productive as possible by doing all the common, repetitive, yet essential, tasks involved in most web development projects.

Ember.js also provides access to the most advanced features of Javascript, HTML and the Browser giving you everything you need to create your next killer web app.

Building Ember.js

  1. Ensure that Node.js and bower are installed.
  2. Run git clone https://github.com/emberjs/ember.js.git && cd ember.js.
  3. Run git config core.symlinks true to ensure that symlinks are enabled.
  4. Run git reset --hard HEAD to reset to HEAD with symlinks.
  5. Run npm install to ensure the required dependencies are installed.
  6. Run bower install to ensure required web dependencies are installed.
  7. Run npm run build to build Ember.js. The builds will be placed in the dist/ directory.

npm install troubleshooting

If you encounter a problem with downloading dependencies like:

npm ERR! registry error parsing json

consider upgrading npm with:

npm install -g npm@latest

You can find more information in Upgrading on *nix (OSX, Linux, etc.) npm wiki page.

Contribution

See CONTRIBUTING.md

How to Run Unit Tests

Pull requests should pass the Ember.js unit tests. Do the following to run these tests.

  1. Follow the setup steps listed above under Building Ember.js.

  2. To start the development server, run npm start.

  3. To run all tests, visit http://localhost:4200/.

  4. To test a specific package, visit http://localhost:4200/tests/index.html?package=PACKAGE_NAME. Replace PACKAGE_NAME with the name of the package you want to test. For example:

To test multiple packages, you can separate them with commas.

You can also pass jquery=VERSION in the test URL to test different versions of jQuery.

From the CLI

  1. Install phantomjs from http://phantomjs.org.

  2. Run npm test to run a basic test suite or run TEST_SUITE=all npm test to run a more comprehensive suite.

From ember-cli

  1. ember test --server

  2. Connect the browsers you want.

  3. If phantom didn't connect automatically, you can run ./bin/connect-phantom-to <optional-port>.

To run a specific browser, you can use the --launch flag

  • ember test --server --launch SL_Firefox_Current
  • ember test --launch SL_Firefox_Current