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

@jimpick/rope-sequence

v1.2.2-3

Published

Rope-based persistent sequence type

Downloads

11

Readme

rope-sequence

This module implements a single data type, RopeSequence, which is a persistent sequence type implemented as a loosely-balanced rope. It supports appending, prepending, and slicing without doing a full copy. Random access is somewhat more expensive than in an array (logarithmic, with some overhead), but should still be relatively fast.

Licensed under the MIT license.

class RopeSequence<T>

static from(?union<[T], RopeSequence<T>>) → RopeSequence<T>

Create a rope representing the given array, or return the rope itself if a rope was given.

static empty: RopeSequence<T>

The empty rope.

length: number

The length of the rope.

append(union<[T], RopeSequence<T>>) → RopeSequence<T>

Append an array or other rope to this one, returning a new rope.

prepend(union<[T], RopeSequence<T>>) → RopeSequence<T>

Prepend an array or other rope to this one, returning a new rope.

slice(from: ?number = 0, to: ?number = this.length) → RopeSequence<T>

Create a rope repesenting a sub-sequence of this rope.

get(index: number) → T

Retrieve the element at the given position from this rope.

forEach(f: fn(element: T, index: number) → ?bool, from: ?number, to: ?number)

Call the given function for each element between the given indices. This tends to be more efficient than looping over the indices and calling get, because it doesn't have to descend the tree for every element.

to may be less then from, in which case the iteration will happen in reverse (starting at index from - 1, down to index to.

The iteration function may return false to abort iteration early.

map(f: fn(element: T, index: number) → U, from: ?number, to: ?number) → [U]

Map the given functions over the elements of the rope, producing a flat array.

flatten() → [T]

Return the content of this rope as an array.