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

derivedarray

v1.0.2

Published

dynamicly derived arrays from another arrays

Downloads

5

Readme

Derived Arrays from another arrays

Functional array methods like .map can be costy since it occurs on all the elements. Even worse when you needed them more than once. Yes you can store the result, but then a change on the main array won't be reflected to your reference. Derived Arrays makes it both - performant and cleaner.

import { RefArray } from "derivedarray"

const users = new RefArray(
	{ name: "Vagif" }, 
	{ name: "Vincent" }, 
	{ name: "Viktor"})
const names = users.derive(user => user.name)

users.push({ name: "Vali" }) // value to users and derivation value to names
names == ["Vagif", "Vincent", "Viktor", "Vali"]
users.shift() // remove first element from users and derived array
names == ["Vincent", "Viktor", "Vali"]

Those methods are wrapped to reflect the changes in derived arrays: .push(), .pop(), .unshift(), .shift(), .splice(), .fill(), .reverse(), .sort(), .copyWithin()

When you want to set a specific index, using .set() method of RefArray is the best method. This will reflect the changes by calculating only the changes you made - users.set(2, { name: "Van" })

Otherwise, you can still use the index setter but this will not update the derived list. To sync them, you can use .refresh() but that will call deriver function for every item in the array and lose all the optimizations, making it almost equal to using .map.

users[2] = { name: "Van" }
users.refresh()

working on a filter version - arrays that are filtered in a performant way when a chage occured on the main array.

working on a generator version - the most optimal version. deriver function will be called for every element when the element is required.