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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@tezka/script-loader

v0.1.0

Published

Dynamic loader of JavaScript files

Downloads

5

Readme

sdk-load-script

This library exports an easy function to load a JavaScript file and make it available to the calling application to run.

See stackoverflow question.

How to use this library:

Step 1. Import the library and configure the ScriptLoader with the list of locations from which one is allowed to load scripts, and optionally list of locations from which loading scripts is prohibited. All rules must succeed in order to load a script, so you can use an allow rule like /path/to/a and a deny rule like /path/to/a/b to allow loading all scripts from /path/to/a except those in the /path/to/a/b subdirectory. You can also add deny rules for system locations from which you know the program should not be loading scripts, for safety, regardless of whatever other rules are later added to allow other locations.

import { ScriptLoader, allowFilePath, denyFilePath } from '@tezka/script-loader';
const loader = new ScriptLoader({
   fileAllowRules: [
      allowFileFromPath('/path/to/plugins'),
      denyFileFromPath('/etc')
   ]
});

Step 2. Use the pre-configured ScriptLoader to load a script:

const pluginBasedir = '/path/to/plugins';
async function doSomething(pluginName) {
   const plugin = await loader.loadFromFilePath(`${basedir}/${$pluginName}.js`);
   // do something with `plugin`
}

Or, if you know the script location is safe because you generate it programmatically and don't accept any use input, you can call unsafeLoadScript with a file URL or absolute file path:

import { unsafeLoadScript } from '@tezka/script-loader';
const pluginBasedir = '/path/to/plugins';
async function doSomething(pluginName) {
   const plugin = await unsafeLoadScript(`${basedir}/${$pluginName}.js`);
   // do something with `plugin`
}