boolbase

What is boolbase?

The boolbase npm package is a very simple utility library that provides two basic functions: one that always returns true and another that always returns false. These functions can be used as default or placeholder callbacks, particularly in scenarios where a truthy or falsy value is needed to determine the flow of logic.

What are boolbase's main functionalities?

Always return true

This feature provides a function that, when called, will always return the boolean value true. It can be used in situations where a callback is required that always approves or passes a condition.

const { trueFunc } = require('boolbase');
console.log(trueFunc()); // outputs: true

Always return false

This feature provides a function that, when called, will always return the boolean value false. It can be used in situations where a callback is required that always rejects or fails a condition.

const { falseFunc } = require('boolbase');
console.log(falseFunc()); // outputs: false

Other packages similar to boolbase

lodash

Lodash is a comprehensive utility library that offers a wide range of functions for manipulating and working with data. It includes methods like _.constant which can be used to create functions that return the same value. Lodash is much larger and more feature-rich compared to the minimalistic boolbase.

underscore

Underscore is another utility library similar to Lodash, providing a range of functions for working with arrays, objects, and functions. It includes the _.constant function for creating functions that return a specific value. Like Lodash, it is more extensive than boolbase.

ramda

Ramda is a functional programming utility library that emphasizes a purer functional style. It includes R.always, a function that returns a function that always returns the same value. Ramda offers a more functional approach and has a broader set of features compared to boolbase.

README

#boolbase This very simple module provides two basic functions, one that always returns true (trueFunc) and one that always returns false (falseFunc).

###WTF?

By having only a single instance of these functions around, it's possible to do some nice optimizations. Eg. CSSselect uses these functions to determine whether a selector won't match any elements. If that's the case, the DOM doesn't even have to be touched.

###And why is this a separate module?

I'm trying to modularize CSSselect and most modules depend on these functions. IMHO, having a separate module is the easiest solution to this problem.