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

@hosseinsaafi/lotide

v1.0.3

Published

The test suite includes several test cases that cover common edge cases and input scenarios. Each test case defines the input values, expected output, and any necessary setup or teardown code. The test code uses Jest as the testing framework and includes

Downloads

3

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 @mhosseinsafi/lotide

Require it:

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

Call it:

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

Documentation

The following functions are currently implemented:

  • function1(head): A commonly used function for arrays is to retrieve the first element from the array. This is often referred to as the "head" of the array.

  • function2(middle): While lodash does support head and tail functions for arrays, it does not have a middle function. Alas, middle is the forgotten child.

  • function3(tail): Instead of the "head", sometimes we need the "tail" of an array. The tail is not the last element of the array. The tail is meant to be every element except the head (first element) of the array.

  • function1(without): This function should take in a source array and a itemsToRemove array. It should return a new array with only those elements from source that are not present in the itemsToRemove array.

  • function1(assertArraysEqual): While the assertEqual is great at comparing primitive types (like numbers and strings), we could use another function for asserting that two arrays are equal.

  • function1(eqArrays): This function compares two arrays for equality. It returns true if the arrays are equal and false otherwise.

  • function1(findKey): Now that we know about callbacks, let's make a more complex version of this in a similar way to what Lodash has.

  • function1(takeUntil): The function 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.

  • function1(Map): map function will take in two arguments: An array to map , A callback function. The map function will return a new array based on the results of the callback function.

  • function1(assertEqual): it would be nice to be able to see a series of success / failure messages printed to the console, letting us know if our functions are behaving as expected.

  • function1(assertObjectsEqual): This function compares two objects, actual and expected, using another function called eqObjects to check if they are equal.

  • function1(eqObjects):This function implementation will require us to further practice problem solving through object key iteration again.

  • function1(findKeyByValue): It will help us search for a key on an object where its value matches a given value.

  • function1(letterPositions): For each letter, instead of returning just one number to represent its number of occurrences, multiple numbers may be needed to represent all the places in the string that it shows up.

  • function1(countLetters): The function should take in a sentence (as a string) and then return a count of each of the letters in that sentence.

  • function1(countOnly): This function should take in a collection of items and return counts for a specific subset of those items. It won't count everything. In order to decide what to count, it will also be given an idea of which items we care about and it will only count those, ignoring the others.

  • function1(flatten): This function takes an array as input and returns a new array with all the elements flattened. Here's how the code works.