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

rina

v0.0.3

Published

Rina Is Not AMD (Asynchronous Module Definition).

Downloads

4

Readme

Rina

Rina Is Not AMD (Asynchronous Module Definition).

Rina Is A Synchronous JavaScript Module Definition, compatible with optimized files produced using AMD format.

Why Rina?

AMD(http://requirejs.org/docs/whyamd.html) is a very instructive guidance, providing a better way for encapsulating complex javascripts in the web today. But ideally, It required you to put modules into each separate file, then dynamic load module once needed.

But in the real world, I usually packaged multiple small js into one big file, gzipped, cached, and delivered by cdn. Path resolving is also a another con to me in some cases (like rails sprockets, BTW I has been used requirejs-rails in a big project, which required me a four-pages requirejs.yml, it's too over).

Require.js also features an optimizer, to bundle all used modules into one single file.

But here is Rina, A smaller and more flexible implementation.


Basically, usage is exactly the same as AMD:

define(['jquery'] , function ($) {
    return function () {};
});
define('myModuleWithSomeLongLongNamespace', ['underscore'] , function (_) {
    return function () {};
});
require(['myModuleWithSomeLongLongNamespace', 'underscore'], function (myModule, _) {
    return function () {};
});

Cause of it's not asynchronous, you may want to do that AMD can't:

myModule = require('myModuleWithSomeLongLongNamespace');

And more examples in: https://github.com/aligo/rina/blob/master/test/test.coffee


Downloads

Production Version (~1kb)

Development Version (~2kb)

Version

0.0.3


Author

aligo Kang [email protected]

License

MIT License