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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@krizvee/lotide

v1.0.0

Published

Lotide is a clone of the lodash JavaScript library with numerous types of functions using JS.

Downloads

18

Readme

Lotide

A mini clone of the Lodash library.

Purpose

BEWARE: This library was published for learning purposes. It is not intended for use in production-grade software.

This project was created and published by me as part of my learnings at Lighthouse Labs.

Usage

Install it:

npm install @krizvee/lotide

Require it:

const _ = require('@krizvee/lotide');

Call it:

const results = _.tail([1, 2, 3]) // => [2, 3]

Documentation

The following functions are currently implemented:

  • head(...): it returns the first item in the array
  • middle(...): it returns the the middle element in an array if array length is greater than 2 else it returns empty array. Also in even case it returns middle two elements.
  • tail(...): it returns all the item in the array except the first one
  • assertEqual(...): this methode compares actual with expected parameters
  • eqArrays(...): it return whether the two arrays are equal or not in a boolen format. It also works for only nesting of arrays.
  • assertArraysEqual(...): it return the equality of two arrays with appropriate message. It also works for only nesting of arrays.
  • without(...): it returnt he array without the second argument from the original array
  • flatten(...): it will flatten the nested array into a flat array
  • countOnly(...): it will count the presence of item within an array of strings based on the object specifying what to count
  • countLetters(...): it should take in a sentence (as a string) and then return a count of each of the letters in that sentence.
  • letterPositions(...): it will return all the indices (zero-based positions) in the string where each character is found.
  • findKeyByValue(...): It will help us search for a key on an object where its value matches a given value.
  • eqObjects(...): it return whether the two objects are equal or not in a boolen format. It also works for only nesting of objects.
  • eqAssertObjects(...): it return the equality of two objects with appropriate message. It also works for only nesting of objects.
  • takeUntil(...): it will return a "slice of the array with elements taken from the beginning." It should keep going until the callback/predicate returns a truthy value.
  • map(...): it works similar to built-in mao function under javascript
  • findKey(...): it takes in an object and a callback. It should scan the object and return the first key for which the callback returns a truthy value. If no key is found, then it should return undefined.