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

js-transducers

v0.1.3

Published

A port of clojure's transducers, plus a few extras

Downloads

10

Readme

xform

Transducers for javascript

Docs

https://boogie666.gitlab.io/js-transducers/#js-transducers

Install

npm install --save js-tranducers

Usage

require("js-transducers/array"); // when using into on js arrays
require("js-transducers/immutable") // when using into on immutable.js collections
const into = require("js-transducers/into");

const xf = require("js-transducers");
const { comp } = require("js-transducers/util");

const process = comp(
  xf.map(x => x + 1),
  xf.filter(x => x % 2 === 0)
);

into([], process, [1, 2, 3]);

util.comp is more or less useless

But it's needed internaly in order to not have any dependencies...

Basically any propper compose implementation will work just fine...

for example Rambda.js:

const process = R.compose(
  xf.map(x => x + 1), 
  xf.filter(x => x % 2 === 0)
);

is identical to:

const process = util.comp(
  xf.map(x => x + 1), 
  xf.filter(x => x % 2 === 0)
);

So feel free to use any compose function you are comfortable with.

lodash compose works in the exact same way.

const process = _.compose(
  xf.map(x => x + 1), 
  xf.filter(x => x % 2 === 0)
);

any other implementation of compose will work in the exact same way, as long as it applies the functions in reverse order

such that if you compose these 3 functions:

function a(x){
  console.log("a");
  return x;
}
function b(x){
  console.log("b");
  return x;
}

function c(x){
  console.log("c");
  return x;
}

the output of the console logs will be "c,b,a".

if the result is "a,b,c" then the transducers need to be used in reverse order.

So with Rambda.js' pipe function the equivalent is:

const process = R.pipe(
  xf.filter(x => x % 2 === 0), // first the filter
  xf.map(x => x + 1) // then the map
);

How the lib is built

Check out (if you know romanian) my talk about this lib and how to build it from scratch here:

https://www.youtube.com/watch?v=z9iuqCsOghc

FAQ

What's with the require("js-transducers/array") or require("js-transducers/immutable")?

js-transducers used a controled from monkey patching in order to add a better version of 'reduce' in order to enable tranducers.

the into tranductions context needs to be have some caracteristics in order to be a propper transduction context.

see https://clojure.org/reference/transducers the 'Creating Transducers' section.