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

fuzzquire

v1.0.2

Published

Fuzzy require modules from your project.

Downloads

32

Readme

Fuzzquire

Easier in-project module loading for cleaner and more readable code.

Fuzzquire is a wrapper around require. You only need to specify the minimum number of file path parts and the file name to load the file in your project, and thus, you increase the code readability as well as reduce the cognitive load on yourself while coding as you do not have to remember the relative file paths anymore. Bliss!

Try it out: npm install fuzzquire --save.

Example

Let's take a directory structure like:

project-folder
├── app.js
├── package.json
├── routes
│   ├── api
│   │   ├── index.js
│   │   ├── notify.js
│   │   ├── services
│   │   │   ├── events.js
│   │   │   └── users.js
│   │   └── typeahead.js
│   ├── auth.js
│   ├── components
│   │   ├── custom
│   │   │   └── pybits.js
│   │   ├── custom.js
│   │   ├── dashboard.js
│   │   ├── index.js
│   │   ├── login.js
│   │   └── portals.js
│   ├── export.js
│   ├── index.js
│   ├── transaction.js
│   └── upload.js
├── utils
│   ├── authentication.js
│   ├── config-loader.js
│   ├── service.constructor.js
│   └── state.js

Now, this is what some file would look before fuzzquire:

const Users = require('../api/services/users');
const auth = require('../../utils/authentication');
const config = require('../../utils/config-loader');
const pybits = require('./custom/pybits');
const app = require('../../app').express;
...

And this would be the same file after fuzzquire:

const fq = require('fuzzquire');
const Users = fq('api/users');
const auth = fq('authentication');
const config = fq('config-loader');
const pybits = fq('pybits');
const app = fq('app').express;

Contributing

Contributions are welcomed. If you want a feature or find a bug, please open an issue and I'll try to resolve it quickly.