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

datastruct

v0.1.0

Published

Various data structures and algorithms written in JavaScript

Downloads

5

Readme

DataStructure

Simple and naïve implementation of some data structure with no dependencies.

  • no OOP (class, extends), just plain Prototypal inheritance
  • no use of dangerous this
  • private internals thanks to Closures
  • no accidential changes thanks to Object.freeze

Currently implemented data structures:

  • Queue
  • Stack

Installing

npm install datastruct

Example usage

import DataStructure, { Queue, Stack } from 'datastruct';

const q = Queue(); // or DataStructure.Queue();
const s = Stack(); // or DataStructure.Stack();

q.add('Hello', 'World!');

q.size();                   // 2
q.length;                   // 2
q.isEmpty();                // false
q.contains('Hello');        // true
q.peek();                   // 'Hello' (.length == 2)
q.members();                // [ 'Hello', 'World!' ]
q.next();                   // 'Hello' (.length == 1)

// creating queue from iterable
const q2 = Queue.of([ 'Hello', 'World!' ]);

// testing for queue
Queue.is(q);                // true

s.add('Hello', 'World!');

s.size();                   // 2
s.length;                   // 2
s.isEmpty();                // false
s.contains('Hello');        // true
s.peek();                   // 'Hello' (.length == 2)
s.members();                // [ 'Hello', 'World!' ]
s.next();                   // 'Hello' (.length == 1)

// creating stack from iterable
const s2 = Stack.of([ 'Hello', 'World!' ]);

// testing for stack
Stack.is(s);                // true

Differences in the order of adding elements

// Queue
q.add('Hello', 'World!') == q.add('Hello'); q.add('World!') == Queue.of([ 'Hello', 'World!' ])

// Stack
s.add('Hello', 'World!') != s.add('Hello'); s.add('World!')
s.add('Hello', 'World!') == Stack.of([ 'Hello', 'World!' ])

s.add('Hello', 'World!')            // members: [ 'Hello', 'World!' ]
s.add('Hello'); s.add('World!')     // members: [ 'World!', 'Hello' ]
Stack.of([ 'Hello', 'World!' ])     // members: [ 'Hello', 'World!' ]

The difference is due to an opinionated decision, that the call s.add('Hello', 'World!') should represent the wish to put these values into stack but when I read them back, give them back in this order or in other words, adding multiple values with one calls implies the order of the values is important and should not be changed regardless of the storage system.

In contrast, adding values with multiple calls implies that you know that Stack is a LIFO structure and wants the values back in LIFO fashion.

License

MIT