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

ok-selector-immutable

v2.0.0

Published

Pluck values from an ImmutableJS object using selector strings.

Downloads

1

Readme

ok-selector

A small library for plucking values out of Immutable objects.

ok-selector supports immutablejs.

Given the following state:

const state = Immutable.fromJS({
  level1: {
    level2: {
      level3: {
        value: 'yes'
      }
    }
  },
  array: [
    {id: 1, value: 2},
    {id: 2, value: 4},
    {id: 3, value: 6},
    {id: 4, value: 8},
  ]
});

These tests hold true

it('should support dot.strings', () => {
  expect(read(state, 'level1.level2.level3.value')).to.equal('yes');
  expect(read(state, 'level1.level2.level3').toJS()).to.deep.equal({value: 'yes'});
  expect(read(state, 'array').toJS()).to.deep.equal([
    {id: 1, value: 2},
    {id: 2, value: 4},
    {id: 3, value: 6},
    {id: 4, value: 8},
  ]);
});

it('should support addressing arrays by id', () => {
  expect(read(state, 'array:3').toJS()).to.deep.equal({id: 3, value: 6});
  expect(read(state, 'array:3.value')).to.deep.equal(6);
});

it('should support plucking all values from an array', () => {
  expect(read(state, 'array*.value').toJS()).to.deep.equal([2, 4, 6, 8]);
});

has

has is like read but returns a boolean response.

Unwrapping

read always returns an object of based on the underlying implementation. Sometimes this is not what you want. unwrap will convert the response of read to a native object. For immutable objects it'll call toJS. Depending on the size and complexity of your state tree this can be relatively expensive.