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

context-loader

v0.1.1

Published

Load scripts and run them in a context. For both browsers and node, sync and async.

Downloads

33

Readme

Context Loader

Load JavaScript, compile the script without running it, run it as many times as you want in as many contexts as you want. Do it in Node or in the browser, with either asynchronous or synchronous loading.

Usage

First. Load context-loader

The main difference between usage in browsers and Node is in initially loading.

// Node
var loadScript = require('context-loader').loadScript;

// Browser
<script src="context-loader.js"></script>

Second. load scripts with context-loader

Script loading can be done in two ways.

//asynchronous
loadScript('path/filename.js', function callback(error, compiledScript){});

//synchronous
var compiledScript = loadScript('path/filename.js');

If loaded synchronously any errors will be passed back as the result

Third. Run compiled scripts in contexts

Once you have the compiled script you can then run it in contexts. State isn't shared inside the script itself so it can be used multiple times in the same or different contexts. In Node, a context is either the global object or a Context object created using the vm module. In the browser a context is either the global object or some other window object like an iframe contentWindow.

// run using the current global context
compiledScript.runInContext();

// node
var initializedContext = compiledScript.runInContext(vm.createContext());

// browser
var initializedContext = compiledScript.runInContext(document.body.appendChild(document.createElement("iframe")).contentWindow);

Return value is the context.