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

require-config

v0.1.2

Published

Dynamically generate a require.config object for the client-side

Downloads

18

Readme

Require Config

A node module to refer to and output (on the server-side) the client side require.js config.

Scope

This library is created to accumulate all good efforts around describing an app's dependencies with a require.config object

...

Install

npm install require-config

Methods

.deps( script )

Adds a new dependency. Accepted formats for script:

  • a string: "%SOURCE%"
  • an object: { "%NAME%" : "%SOURCE%" }
  • an array: [{ "%NAME%" : "%SOURCE%" }, { "%NAME%" : "%SOURCE%" },...]

.shim( name, options )

Setup shims for each javascript file.

The options is not mandatory and if a 'known' shim is found it will always override the options passed.

In addition, if autoshim is enabled the shim will be enriched by including the previous script in the (individual) deps list.

.paths( name, script(s) )

Add a new path for a script (name). Usually automatically added with each dependency - can be called manually to include fallback script locations...

.set( options )

A wilcard method to create any configuration options, not only in deps, shim,paths.

.render()

Outputs the whole configuration in a JS object. Accepts no options (currently)

.build()

Like render but optimizing config for r.js compilation

Parameters

cache

A boolean option to set (or not) a cache busting variable at the end of each script. In the require.js docs this is mentioned as urlArgs.

Default is true

autoshim

A boolean option to attempt to automatically create shims for every file. The current implementation is vary basic, basically requiring the previous script in the deps of the each script. A short list of shims for popular js libs is included (in a static form) - more to be included in later releases.

Default is true

Usage

// initiate lib
var r = require("require-config")({ cache : false });

// set base folder
r.set({ baseUrl : "/assets/js" });

// add some dependencies

// - as a plain string:
r.deps("//ajax.googleapis.com/ajax/libs/jquery/1.8.3/jquery.min");

// - or an object:
r.deps("//ajax.googleapis.com/ajax/libs/jquery/1.8.3/jquery.min");

// finally render the js object
r.render()

While rendering a view you can output the config as a JSON:

output +=  '<script type="text/javascript">var require = '+ r.render({ string: true }) +'</script>';

Roadmap

  • Read config from package.json (using require-package)

  • Parse rendered view and include script tags in the configuration

Credits

Created by: Makis Tracend

Distributed by Makesites.org

Released under the MIT license