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

quokka-plugin-subdir

v0.1.0

Published

Quokka plugin to resolve imports from subdirectories modules, while in scratch mode.

Downloads

108

Readme

quokka-plugin-subdir

Small quokka plugin for resolving node_module imports from subdirectories

But why?

I am using quokka mostly in "scratch" mode to check/test small pieces of code that uses project node_modules. In general it's not a problem until you have some kind of monorepo, so there is a lot of subdirectories with their own modules, even tho it's not a problem until you are doing this in scratch mode.

Scratch mode will relate on repo root directory, trying to load modules from repo/node_modules, in this case the only option is to write full relative path.

Usage

Add plugin to quokka config:

{
  "plugins": ["quokka-plugin-subdir"],
}

can be used in two ways, let's say you have monorepo with 2 projects in it:

my-monorepo-project
├── client
├── server

First way is adding "subdir" into config:

{
  "quokka": {
    "plugins": ["quokka-plugin-subdir"],
    "subdir": "client"
  }
}

(can be added directly in quokka file, see details)

With above configuration:

const _ = require('lodash')

is equal to:

const _ = require('./my-monorepo-project/client/node_modules/lodash')

Second way is adding tilda symbol before import:

const koa = require('~server/koa')

is equal to:

const _ = require('./my-monorepo-project/server/node_modules/koa')

By default imports prepended with tilda will have advantage over subdir config

Install

You can install it as dev dependency for your package:

Yarn

yarn add --save --dev quokka-plugin-subdir

NPM

npm install --save-dev quokka-plugin-subdir