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

@abradley2/cycle-effects

v4.2.0

Published

Convenient catch-all driver for effects in Cycle.js

Downloads

14

Readme

Cycle Effects

npm install --save @abradley2/cycle-effects

Purpose

When using Cycle, especially on the server, there's often need for a large amount of complex drivers dealing with a large amount of side effects.

This library assumes you are using xstream and the default @cycle/run. If you are interested in using this without another Reactive Programming library that Cycle supports, please open an issue

API

As with most other Cycle drivers, the API surface area is just a source and a sink.

The types are a good guidance on what is expected. See the Example Usage section for a full, in-depth guide.

declare module '@abradley2/cycle-effects' {
  export type EffectSource<A> = (tag: string | symbol) => xstream<{
    value: A;
    error: Error;
  }>

  export type EffectSink<A> = xstream<{
    run: (args: any) => Promise<A>;
    args: any;
    tag: string | symbol;
  }>
}

But isn't this running effects where we should be pure??

Actually, no. Similar to Redux Loop we are only returning a side-effect causing function to be executed by the runtime. This is why we must supply an args property to the effect configuration in order to pass anything to a function that creates side effects.

Example Usage

The following application will first run an effect to get a random number, and then run an effect that sets a timeout with a duration based on that random number. Finally, that effects results in the name "Tony" being sent through the result sink.

const xs = require('xstream').default
const createEffectsDriver = require('@abradley2/cycle-effects')

function application({effects}) {
	const randomEffect = Symbol('randomEffect')
	const timeoutEffect = Symbol('timeoutEffect')

	return {
		effects: xs.merge(
			xs.of(
				{
					run: () => new Promise(resolve => resolve(Math.random())),
					tag: randomEffect
				}
			),
			effects.select(randomEffect)
				.map(randomNum => {
					return {
						run: (name, timeoutDuration) => new Promise(resolve =>
							setTimeout(() => resolve(name), timeoutDuration)
						),
						tag: timeoutEffect,
						args: ['Tony', randomNum * 1000]
					}
				})
		),
		result: effects.select(timeoutEffect)
			.filter(result => !result.error)
			.map(result => result.value)
	}
}

const {sinks, run} = setup(application, { effects: createEffectsDriver() })

sinks.result
  .take(1)
  .subscribe({
    next: function (value) {
      console.log(value) // "Tony"
    }
  })