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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@allquire/core

v0.1.5

Published

Require from anywhere & Typescript dynamic require.

Readme

npm

Language I18N PRs Welcome License

Require from anywhere & Typescript dynamic require.

🌟 Features

  • Require from anywhere.

Feel free to require even the module hasn't been installed. Packages will be installed when the allquire() calls for the first time.

This greatly increases the convenience for users to use the program. Imagine a scenario that a system has many extensible plugins, but users only want to use a few plugins usually. In this case, it is not appropriate to include all plugins in the application package.

AllQuire is an excellent solution to this problem. You can let users provide a list of plugins with options into a config file, and import it using cosmiconfig, or use the companion GUI to generate the list for your application.

An example working in progress is VkiQ.

  • Typescript dynamic require.

Typescript is not as flexible as JavaScript because it does not support changing the module ID of require at runtime. Use AllQuire to dynamically provide module ID and require the module you want.

Imagine a scenario that your Typescript backend service needs to dynamically import all routes from the api folder and apply them when it starts. At this time, you may need to use for.. of to traverse each route, but Typescript does not support dynamically providing the module ID that needs to be required.

AllQuire can solve this problem. Just use allquire(route) to require them.

💨 Install

Install with yarn:

yarn add @allquire/core

Install with npm:

npm i -S @allquire/core

👉 Usage

Use with JavaScript:

const allquire = require('@allquire/core')
const greeting = await allquire(
  'https://npmjs.com/package/@allquire/hello-world'
)
console.log(greeting()) // Hello World!

Use with TypeScript:

import allquire from '@allquire/core'
const greeting: HelloWorld = await allquire(
  'https://npmjs.com/package/@allquire/hello-world'
)
console.log(greeting()) // Hello World!

💬 BUGs & Issues

Feel free to open issues.

💻 Contributions

PRs are welcome! Feel free to contribute on this project.

Plugin Contributions

Feel free to make AllQuire Plugins and add a line in plugins.js!

⚠ LICENSE

MIT