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

require-sliced

v1.0.2

Published

merge a single module source from multiple files

Downloads

11

Readme

workflow Jest coverage

require-sliced is a node.js library implementing tools for working with modules whose source code may be partitioned across multiple eponymous files located in different directories.

Consider a large application with the business logic implemented as a set of modules organized in topical directories, say /crm, /hr and so on. It may be convenient to have a common users module with some methods and properties defined in /crm/users.js and others in /hr/users.js. require-sliced lets developers do just that: it features the ModuleMap class designed to act as a registry of modules given as sets of partial source files to be assembled with subclassable-object-merger.

ModuleMap tracks files' modification times and can clean up the require.cache to always yield the last version, which is handy for development environments, but can be turned off with the watch option to avoid the related performance overhead.

Installation

npm i require-sliced

Usage

const {ModuleMap} = require ('require-sliced')

const codeRegistry = new ModuleMap ({
  dir: {           // see https://www.npmjs.com/package/fs-iterators
    root: ['/opt/myProject'], 
//    filter: (str, arr) => arr.at (-1) === 'API', // **/API/*
//    live: false,
  },
// ext: '.js',
// watch: false,   // uncomment to suppress checking for modifications
// merger: new myObjectMerger (someOptions)
})

codeRegistry.load () 
  // all at once: makes sense when watch === false

const usersModule = codeRegistry.get ('users') 
  // merge from all `require ('/opt/myProject/**/API/users.js')`

usersModule.select () // for example

// or just

codeRegistry.getMethod ('users', 'select') ()