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

@yimura/import-dir

v0.1.12

Published

Helper to asyncronously import directories.

Downloads

42

Readme

importDir()

This is an esModule implementation of the following module: https://github.com/aseemk/requireDir

I've tried to port as many of its features that seem useful or usable with esModules.

Currently only .js files are supported as .json files are only available with experimental flags.

With esModule an async module loader is used and to allow flexibility you need to await the each key of the object when you want to use it.

Restrictions

Currently esModules are not aware of the parent module they've been imported from. This means that an absolute path needs to be passed. If you try to pass a relative path, this will return an error.

I can add support for relative paths later on but currently this can only be achieved with experimental launch flags, if an issue is opened on GitHub, I'll take a look at adding it.

Proposed solution

You can use resolve to get the absolute path of a relative path.

import { resolve } from 'path'
import importDir from '@yimura/import-dir'

const import = importDir(resolve('./dir/'));

Example

Given this directory structure:

dir
+ a.js
+ b.json
+ c.coffee
+ d.txt
+ e.js

importDir(resolve('./dir')) will return the equivalent of:

{
  a: Promise<import('./dir/a.js')>,
  e: Promise<import('./dir/e.js')>
}

Installation

npm install @yimura/import-dir

Usage

Basic usage that examines only directories' immediate files:

import { resolve } from 'path'
import importDir from '@yimura/import-dir'

let dir = importDir(resolve('./path/to/dir'));

You can optionally customize the behavior by passing an extra options object:

let dir = importDir('/path/to/dir', { recurse: true });

Options

recurse: Whether to recursively import() subdirectories too. (node_modules within subdirectories will be ignored.) Default is false.

recurseDepth: Set how deep we have to recurse.

noCache: Prevent file caching. Could be useful using gulp.watch or other watch requiring refreshed file content Default is false.

let dir = importDir('/path/to/dir', { noCache: true });