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

morgas

v0.8.8

Published

dependency free framework for fun

Downloads

4

Readme

Morgas.js

JavaScript data processing framework for fun

ImportManager

tests

Usage

  • Browser
<script defer src="Morgas.js"></script>
  • Node
    1. cli
      npm install morgas
    2. js
      require("morgas");
      // creates global "Morgas" and "µ" namespaces
    In Node context every module is available via µ.getModule("<name>").

##Node custom modules In order to load custom modules you need to

µ.addModuleRegister(register,baseDir);
// or
µ.addResourceFolder(folder);

In resource folders the filename is automatically also the module name.

##Build npm build script for bundles

npm run build <bundleName.js> <module> [module [...]]

output

build/bundleName.js
build/bundleName.js.map

You can also write your own script with require("Morgas/lib/dependencyParser") and µ.getModule("DependencyResolver").

##dependencyParser checks for

SC=SC({
	[...]
});

and parses every shortcut as "use" dependency and every GMOD("<moduleName>") before that as "hard" dependency.

therefore it is recommended to use an IIFE like this:

(function(µ,SMOD,GMOD,HMOD,SC){
	
})(Morgas,Morgas.setModule,Morgas.getModule,Morgas.hasModule,Morgas.shortcut);