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

mod42

v1.0.0

Published

Until I finalize the different recipes, it might not be a bad idea to build them incrementally.

Downloads

4

Readme

Until I finalize the different recipes, it might not be a bad idea to build them incrementally.

How about:

Mod1: most basic, probably starts with a Base, and adds something

var Base = require("base42") --> pick the most useful "base" module recipe Base.Base1 Base.Base2 Base.Base3 ...

Maybe the exported "chosen"/default class isn't even the last one... If you need more features, you can use one of the later verisons:

Base === Base.Base3, for example Base.Base4, Base5, or BaseWhatever are the additional versions

Then, for Mod, we do the same thing

Mod1 = probably the default Base.extend, but it doesn't really matter...

then Mod2 = Mod1.extend

+++++++++++++

Mfn, SetMfn, and ExtendMfn are all part of the Module, and their functionality is intertwined.

Can we make sub-folders for Mod1, Mod2, etc? And have a "set.js" that exports a SetMfn.make({}); ??