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

@axoncodes/xjs

v1.1.0

Published

Better quality time with JS

Downloads

17

Readme

This module has got simple solutions so that you wouldn't need to focus on the chores

IF

Instead of going through long if statements just to make sure an object-nested property exists, do it just once:

Example:

If you're looking for the myobj.names.age.grade in an object, which means, you would have to write a long if statement, instead, you can do this:

xjs.if(myobj, 'myobj.names.age.grade')

OR

When you want to just select the fist valid variable in a bunch of them, just list the vars as array, and we shall answer you in a matter of a second

Example:

 xjs.or([contour[key.replace(/x/g, 'y')], prevY])

MAP

When you use the 'map', the good thing is that it returns the data directly back to you unlike 'forEach', but the one thing that I hate, is that if you would try to process the inputes of the array given to the 'map' and then decide to whether return the answer or not, on false, it returns you null

So here we are, no extra step or forEach required:

Example:

return xjs.map(fontJson, tag => 
  tag.tag == 'glyph'
    ? return tag.attributes.unicode.replace(/-/g, '_')
    : null
)