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

amashi-imports

v1.0.0

Published

dynamic module importing

Downloads

2

Readme

amashi-imports

dynamic commonjs importing

docs

examples

for these examples we'll be using this to set the value

function setValue(amount){
    var fs = require('fs');
    fs.writeFileSync("./tmp/test.js", `module.exports = ${amount};`);
}
const Require = require("amashi-imports");

setValue(0);

const req = new Require("./tmp/test.js");
req.Load(); // this will load your module
console.log(req.value); // 0
setValue(1)
console.log(req.value); // 0

ok cool so you could already do that but here's the fun part

const req = new Require("./tmp/test.js");
req.Load(); // this will load your module
console.log(req.value); // 0

req.Reload(); // this will reload the module

setValue(1)
console.log(req.value); // 1

you can reload the module that way if you make a change to a file you can tell the script to update it to the current without having to update everything else to share a value

actual documentation

this will create a basic require instance

const req = new Require("file path");
console.log(req); // Require("file path")

this will create a require instance but verify the file path to make sure we aren't going to cause future errors.

const req = Require.Import("file path");
console.log(req); // Require("file path")

this will do the same thing except it'll be asynchronous

const req = await Require.AsyncImport("file path");
console.log(req); // Require("file path")
req.Load(); // this will load a module
req.Unload(); // this will unload a module
req.Reload(); // this will reload a module

we also offer asynchronous options

await req.AsyncLoad(); // this will load a module
await req.AsyncUnload(); // this will unload a module
await req.AsyncReload(); // this will reload a module

any | req.value the value of the module.exports. boolean | req.inCache this will tell you if it's in cache. NodeModule | req.cacheValue this will get the value of the module in the cache. object | req.path this will tell you a lot of pathing info across different systems ex: linux & microsoft. string | req.require_resolved this will return the value of require.resolve(filepath). boolean | req.fileExists this will tell you if the file exists