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 🙏

© 2026 – Pkg Stats / Ryan Hefner

ember-addon-test

v0.0.0-alpha.1

Published

[![npm version](https://badge.fury.io/js/ember-addon-test.svg)]()https://www.npmjs.com/package/ember-addon-test

Downloads

13

Readme

ember-addon-test

npm versionhttps://www.npmjs.com/package/ember-addon-test

Test your v2 ember-addons with ease without any boilerplate files.

Running Tests

In your addon's directory, run:

pnpm addon-test

or

yarn addon-test

or

npm exec addon-test

In CI

Tests will run to completion with exit status 0 for success and 1 for failure. This is determined by [ci-info][npm-ci-info] in the shell env. [npm-ci-info]: https://www.npmjs.com/package/ci-info

Conventions

a file named /tests/setup.ts must exist so that your tests can be bootstrapped.

It should contain your test setup and import all your test files. This is powered by vite, so we can import all tests with one line. Minimally, you'll want something like this:

import * as QUnit from 'qunit';
import { setup } from 'qunit-dom';

setup(QUnit.assert);

import.meta.glob('./**/*test.{js,ts}', { eager: true });

For adding types for import.meta, you'll need to install vite and following these instructions

Using your own vite.config.mts

mts is required because only ESM is supported. By default .ts files in node are converted to CJS, even if they use imports. Using the mts extension prevents this.

You can import the plugins provided by this library for your own vite config like this:

// vite.config.mts
import { defineConfig } from 'vite';
import { addonTest } from 'ember-addon-test';

export default defineConfig({
  plugins: [
    ...addonTest(),
  ],
});

Testing against multiple ember versions / compiler settings

This is not supported at this time, ember-addon-test is still considered experimental, and doesn't yet support swapping out the ember-source version (yet). Testing against different ember versions is a great need for the entire ecosystem, so this will be implemented eventually.