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

bethlehem

v1.9.0

Published

A minimal, practical functional programming library for JavaScript

Downloads

4

Readme

bethlehem

Github Actions Status Github Pages Status codecov npm weekly downloads

Bethlehem is a minimal functional programming library for JavaScript. It is inspired by Ramda but has some significant differences.

Usage

First, install bethlehem (tips: because there are known problems before v1.3.0, it is better to set your minimum version of bethlehem to 1.3.0):

yarn add bethlehem@^1.3.0
# or npm
npm i bethlehem@^1.3.0

Then, cherry-pick the function(s) you want:

import { compose, add } from 'bethlehem'
// you can use cjs if you don't want tree-shaking
const { compose, add } = require('bethlehem')

Or import everything:

import * as B from 'bethlehem'
// you can use cjs if you don't want tree-shaking
const B = require('bethlehem')

Because bethlehem specified ESM build file in the module field of package.json, your module bundler will do tree-shaking for you.

If you want to use bethlehem without any bundler with your browser, you can use the UMD build. Add a script tag to your HTML file:

<script src="https://unpkg.com/bethlehem/dist/b.umd.production.js"></script>

And you can access everything in the B global variable.

Documentation

Benchmark

The benchmarks between bethlehem, ramda and rambda is still a work in progress. There is an external repo that stores some benchmark data about possible internal implementations of bethlehem.

Development

Before running any command, install all the dependencies using yarn install or npm install.

yarn watch
# or npm
npm run watch

This will run ava in watch mode. Test suite will be rerun if there's any change in src or in the test file.

yarn test
# or npm
npm run test

This will run ava in verbose mode. All test suites will be ran and their titles will be displayed in the output.

yarn build
# or npm
npm run build

This will build all source code and put them in the dist folder. Declarations will be also built.

yarn build:docs
# or npm
npm run build:docs

This will build the documents into the docs folder using TypeDoc.