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

shlyce

v1.0.1

Published

Fast view into a subarray with an Array-like interface

Downloads

5

Readme

Shlyce

Fast view into a subarray with an Array-like interface. Assignments to the Shlyce mutate the underlying Array.

NPM version Build Status

Examples

const Shlyce = require('shlyce');
const arr = [1,2,3,4,5];
const shlyce = new Shlyce(arr, 1); // Takes O(1) time, no data is copied
shlyce.length === 4;
shlyce[0] === 2;
shlyce[0] = 99; // Mutates the underlying array
arr[1] === 99;

Benchmarks

Shlyce slices in constant time and space, while Array.slice returns a new array, requiring linear time and space to copy. This difference can speed up our code tremendously.

Consider a recursive binary search of N elements:

N=250,000
Shlyce x 21,719 ops/sec ±2.09% (76 runs sampled)
[].slice x 935 ops/sec ±2.63% (71 runs sampled)

N=500,000
Shlyce x 20,628 ops/sec ±1.95% (80 runs sampled)
[].slice x 386 ops/sec ±2.77% (67 runs sampled)

N=1,000,000
Shlyce x 18,481 ops/sec ±1.94% (76 runs sampled)
[].slice x 180 ops/sec ±2.72% (65 runs sampled)
Fastest is Shlyce

Note that a well implemented binary search should run in O(log(n)) time. Using [].slice we only get O(n) time 'cause we're copying half the array for each slice.