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

@attack-monkey/impure

v1.0.1

Published

A light-weight wrapper for managing impure code

Downloads

15

Readme

impure

A light-weight wrapper for impure code

Checkout: https://github.com/attack-monkey/Lean-Functional-Typescript

Install


npm i @attack-monkey/impure

Use


import { impure } from '@attack-monkey/impure'

Impure Code

Impure code should have no effect on the Pure Code around it.

To achieve this, impure code should not leak impurity into the scope.

Take console.log('cat'). It is impure because it sends data out of the Pure Function, and prints 'cat' to the console. In other words it interacts with more than just inputs, constants and other 'pure' functions. In functional programming terms - it has a side-effect. console.log('cat') however doesn't leak scope, and so is fine to use in Lean (https://github.com/attack-monkey/Lean-Functional-Typescript).

If on the other hand we have:


let a = Math.random()
a = a + 1

^^ This code is definitely impure, since Math.random() produces a random number and then a is mutated after creation. Moreover, it leaks impurity by assigning a random value to the variable a - so this code is not ok to use.

The above code could be rewritten as


const a = Math.random()
const b = a + 1

^^ ... which removes the mutation, but note that a is still impure due to having a random value.

Impure code like this can be wrapped in a wrapper that contains the leakage.

eg.


impure(() => {
  const a = Math.random()
  const b = a + 1
  return [a, b]
})
  .then(([a, b]) => a + b)

impure().then() is void of value regardless of what it contains, and doesn't leak any impurity.

The impure code is wrapped in a function, and the result is passed to the pure function inside the then.

Here's the async version.


asyncImpure(resolve => {
  setTimeout(() => {
    resolve(getRandom())
  }, 1000)
})
  .then(a => a + 100)

Both feel alot like the familiar Promise syntax that we are used to.

So what benefit does this provide?

Well it forces developers to think about pure vs impure for a start. More than that though, it means that there is a focus on writing pure functions that are easy to test. While the impure code may need to load some values using getters, the tricky logic is handled by pure operations.