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

@collectable/core

v5.0.1

Published

[Collectable.js] Core Module

Downloads

1,925

Readme

Collectable.js: Core Module

Build Status NPM version GitHub version Gitter

This module provides functionality that is internal to Collectable.js data structures. You do not need to take it as a dependency directly.

For unit testing during development set VSCode to build (CTRL/CMD-SHIFT-B; the task is set to watch/rebuild on changes), then, from your terminal/console in this directory, run one of:

$ npm run test-dev
$ yarn run test-dev

The project will compile, Mocha will run in watch mode and bail when encountering a failing test. Because VSCode is building in watch mode too, making a change will recompile source files, and the compiled outputs will be picked up automatically picked up by Mocha and rerun.

This development testing process is independent of the main Gulp-based build and exists only to make development easier. Build with Gulp after you're satisfied that source code and tests work correctly.