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

functional-arrays

v1.0.1

Published

For all your array functional needs!

Downloads

1

Readme

Functional Arrays (functional-arrays)

For all your array functional needs!

Do you like functional programming and curry functions? Do you also detest the thought of those pesky parenthesis? Then you've come to the right place!

Introducing "functional arrays" – a new way to call functions.

Table of Contents

Background

Every since I can remember I have been a fan of Javascript, but recently I felt like something was missing, there was just something just didn't resonate with me. After years of working with Javascript through thick and thin, through difficult and fun times, it finally hit me!

What Javascript, and a lot of other programming languages, are not understanding with it's narrow-minded and petty design approach for the language is: parenthesis are evil. And far less superior to it's much more versatile cousin; the curly brackets.

This library is a start to bring back harmony into this world we Javascript developers have to live in. It's not solving all the issues sadly (see Limitations), but it's a beginning of something bigger, a step towards a world we can see ourselves living in – together!

Install

All you have to do to install functional-arrays and start your journey towards greatness is to run the following command if you are using Yarn:

$ yarn add functional-arrays

or if you are using NPM

$ npm install --save functional-arrays

Usage

It's as simple as importing the createArrayFunction from the functional-arrays package and using it as follows:

import { createArrayFunction } from 'functional-arrays'

const greeter = (name: string, country: string): string => {
  return `Hello ${name} from ${country}!`
}

const superAwesomeGreeter = createArrayFunction(greeter)

const output = superAwesomeGreeter['Johan']['Sweden']

console.log(output) // "Hello Johan from Sweden!"

Limitations

Due to Javascript being non-believers in the "no parenthesis movement" there are limitations, the most prominent one is that indexes for arrays or objects (even if given as numbers or symbols) are in the end strings, meaning all our parameters needs to be strings. But fear not, we can utilize such amazing (but parenthesized) functions such as Number.parseInt(), JSON.stringify(), and JSON.parse().

We hope that one day Javascript realizes the mistakes it is doing with forcing this limitation and utter nonsense upon us.

FAQ

1. Why?

Yes.

License

MIT © Johan Jansson