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

import-file

v1.4.0

Published

import the closest file as a node module with loader

Readme

import-file

Build Status

Import the closest file as a node module with loader.

What is it

Say you're writing a CLI tool. You may want the following features:

  • Get the closest configure file
  • Automatically register module loader according to extension name

import-file manages these for you.

Example

/project/my_config.babel.js
export default {
    name: 'awesome',
};
/project/src/index.js
const importFile = require('import-file');
const config = importFile('my_config.babel.js');
console.log(config.name);
$ cd /project/src && node index
# => `awesome`

Usage

importFile(filepath[, options])

Import a file as a node module. Return a node module if the file exists, otherwise throw an error.

Arguments
  1. filepath (String): Target file path. If not provide a extension name, it will automatically add extension and register module loader. For more detail of extensions and modules, please read interpret.
  2. options (Object): These are all the available options.
    • cwd (String): The directory resolves from. Defaults to process.cwd()
    • useLoader (Boolean): Enable automatically register module loader according to the adding extension name. Defaults to true
    • useFindUp (Boolean): Find by walking up parent directories. Defaults to true
    • useCache (Boolean): Cache imported file. The same behaviour with node.js require. Default to true.
    • useESDefault (Boolean): Export default in ES module. Default to true.
    • resolvers ([String]): Tell importFile what directories should be searched when resolving files
    • exts ([String]): Extensions white list for loader. Only work if useLoader is true. Defaults to all interpret extensions

importFile.resolve(filepath[, options])

The same with importFile(), but just return the resolved filename. Throw an error if the file is not exists.

Installing

$ npm install import-file

License

MIT