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

@khalyomede/prototype-storm

v0.2.1

Published

Supercharge your Javascript!

Downloads

6

Readme

Prototype Storm

Supercharge your Javascript!

https://npmjs.org/@khalyomede/prototype-storm npm bundle size NPM Snyk Vulnerabilities for npm package Build Status

Summary

About

I created this library because I saw on StackOverflow and Dev.to people using Underscore.js and Loadash. After I took a look, I thought "why do they use functional programming, while Javascript has this inner power with chainable prototypes?".

For many, the issue was to keep Javascript immutable, for others it was that Prototypes are "unsafe" because they could broke existing function. None of those explaination convinced me, because prototypes are immutable by default, and I can manage to not break existing function by checking if the prototype already exist or not in the object.

So I decided to give it a try.

Installation

With NPM:

npm install @khalyomede/prototype-storm@0.*

Usage

With Node

You can either do tree shaking over the prototypes you which to take:

import { max, radians, absolute } from "@khalyomede/prototype-storm"; // Supercharge the object Number with "radians", and "absolute", and the object Array with "max", so do not use those variables directly

const numbers = [-12, -41, -87];

numbers
	.max() // -12
	.radians() // -0.20943951
	.absolute(); // 0.20943951

Or import the whole prototypes:

import "@khalyomede/prototype-storm"; // Every objects have been supercharged!

Prototypes documentation

You can find the full documentation here: prototypes.