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

node-hook-filename

v1.0.0

Published

"Hooking node require calls for specific extensions to only return the filename"

Downloads

49

Readme

Circle CI

node-hook-filename

Hooking node require calls for specific requests to only return the filename or the return value of a callback.

Usage

Returning filename

const nhf = require('node-hook-filename')

nhf([ /\.scss/, /\.svg/ ])

const scssAsset = require('../path/too/filename.scss')
const svgAsset = require('../path/too/filename.svg')
const normalRequire = require('../path/too/js/file')

// scssAsset === '../path/too/filename.scss'
// svgAsset === '../path/too/filename.svg'

// normalRequire is unaffected

Passing a callback function

const nhf = require('node-hook-filename')
nhf([ /config/ ], (filename) => 'foo ' + filename)

const configRequire = require('config')
// configRequire will return 'foo config'

Handy if you are running a universal/isomorphic app that requires asset files.

This is mostly useful for testing and not production ready!

Greatly influenced by https://github.com/bahmutov/node-hook

Bonus

There's a normalize function you can supply as callback if you like

const nhf = require('node-hook-filename')
nhf([ /config/ ], nhf.normalize)

const file = require('./file-in-my-app')
// file === '/my-ap/file-in-my-app'

This is handy to avoid absolute URLs whilst enforcing consistency

It assumes you are running commands from the root of your project