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

@kbase/common-es6

v0.12.3

Published

JS ES6 AMD modules commonly used in kbase-ui and friends

Downloads

10

Readme

KBase UI ES6 Library

Testing

Unit testing ES6 AMD modules?

In this project, we create unit test modules in-situ with the module they are providing tests for.

This makes for self-documenting tests.

However the challenge is that the tests are written as AMD modules. This makes sense since they are colocated with their target modules, and the same module construction while not necessary is easier to understand. It fits the way the modules are to be used by consumers.

However, the test runner will be command-line based using nodejs. This creates a barrier between the test runner and the tested code.

One approach is to utilize requirejs in node. This is the initial approach chosen here. This facilitates very fast test running, which can be conducted during coding sessions to provide immediate feedback.

The end user tool is a makefile (make test). This also makes it easy to integrate into a consuming project. After all, how is the consuming project to evaluate the quality of the library without running tests itself? This is the strategy of some newly-engineered languages and toolsets, such as golang.

Another approach would be (and will be utilized here) to utilize nodejs to manipulate test sessions using a headless browser. This requires quite a bit of extra setup, from installing local browsers, to creating a local test server to provide the files to the server, and creating an index page to serve and execute the test scripts.