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

jscope

v0.1.1

Published

JScope is a inherital prototype factory.

Downloads

26

Readme

JScope

Build Status Coverage Status Climate Status Issues Open Issue Resolution

Version Node Downloads Slack Status License

JScope

NPM GRID

Motivation

Sometimes when you try write elegant code with fallback values you write something like this:


  // The Common case

  var foo = function(options){

      // Ensure option value to prevent undefined value
      options = options || {}; // !!WARNING This line do not force the value type, so if the object passed is not a plain object it will broke your code

      /*************************************/
      /* Default value fallback resolution */
      /*************************************/

      // Solved with ternary operator
      options.bar  = options.bar ? options.bar : 'foo';

      // Solved with if statement
      if(!options.bar)
        options.bar  = 'foo';

      // Solved with stream conditional operator
      options.bar  = options.bar || 'foo';

      return options;
  }

Let's do it easier!!


  // The JSCope case

  var jscope = require('jscope');

  var foo = function(options){
      options = jscope({
          'bar': 'foo',
          'foo': 'bar'
      }).$new(options);

      return options;
  }

  var result = foo({
      'frog': 'croac!',
      'bar': 'mooo'
  });

  // 'croac'
  console.log(result.frog);
  // 'bar'
  console.log(result.foo);
  // 'mooo'
  console.log(result.bar);
  // 'foo'
  console.log(result.$$root.bar);
  // 'foo'
  console.log(result.$$parent.bar);

  var child = result.$new({
      'bar': 'wow!!'
  });

  // 'foo'
  console.log(child.$$root.bar);
  // 'foo'
  console.log(child.$$parent.$$parent.bar);
  // 'mooo'
  console.log(child.$$parent.bar);
  // 'wow!!'
  console.log(child.bar);

As you can see you keep the data with persistence, and it's accesible by $$parent or $$root nodes, so your data never were so sure!!

Installation

Install with npm install jscope --save.

WTF