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

js-vextensions

v1.0.80

Published

Extensions for Javascript, by Venryx.

Downloads

179

Readme

JS - VExtensions

Extensions for Javascript, by Venryx.

Installation

npm install js-vextensions --save-exact

The --save-exact flag is recommended, since this package uses Explicit Versioning (Release.Breaking.FeatureOrFix) rather than SemVer (Breaking.Feature.Fix).

To let npm increment FeatureOrFix (recommended), prepend "~" to its version in package.json. (for Breaking, prepend "^")

Using class methods/extensions

Approach 1: (as class methods/extensions)

Setup:

// To add the class-extension typings (so typescript knows the class/prototype contains those methods)
// /// <reference path="../node_modules/js-vextensions/Helpers/@ApplyCETypes.d.ts"/> // type import approach A
// import "js-vextensions/Helpers/@ApplyCETypes"; // type import approach B
type __ = typeof import("../node_modules/js-vextensions/Helpers/@ApplyCETypes"); // type import approach C (recommended)

// To actually add the methods to the class-prototype chain (so it works at runtime)
import "js-vextensions/Helpers/@ApplyCECode.js";

Usage:

const array = [1, 2, 3];
console.log(array.Skip(1)); // logs "2,3"
Approach 2.A: (using wrapper, with type specified)
const array = [1, 2, 3];
console.log(ArrayCE(array).Skip(1)); // logs "2,3"
Approach 2.B: (using wrapper, with type inferred)
const array = [1, 2, 3];
console.log(CE(array).Skip(1)); // logs "2,3"
Approach 3: (using standalone functions)
const array = [1, 2, 3];
console.log(ArrayCES.Skip(array, 1)); // logs "2,3"