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

workspace-alias

v0.1.0

Published

Get aliases for your workspace packages for the other tools

Readme

workspace-alias

Forked from lerna-alias.

Simple package for getting alias object for packages managed by npm or yarn workspaces, so other tools (such as webpack, rollup, jest and possibly more) can consume your packages directly from the source files, instead of the built and prepared distribution files.

It just eases development and setting up scripts depending on other monorepo packages.

API

workspaceAliases({
  // from which directory monorepo should be searched for
  directory: string = process.cwd(),
  // optional array of `mainFields` that should be used to resolv package's entry point
  // similar to the https://webpack.js.org/configuration/resolve/#resolve-mainfields
  // using this takes precedence over default `sourceDirectory` option
  mainFields?: string[],
  // which directory should be considered as containing source files of a package
  // if specified as false it will use package's root and rely on a tool's (i.e. webpack) resolving algorithm
  sourceDirectory: string | false = 'src'
}): Aliases

Types

Aliases

type Aliases = {
  // value is a local directory path to the package
  // resolved using `sourceDirectory` and `mainFields` options
  [packageName: string]: string,
}

Usage

with webpack

const { webpack: workspaceAliases } = require('workspace-alias')

module.exports = {
  // ...
  resolve: {
    // ...
    alias: workspaceAliases(),
  },
}

with Rollup

const { rollup: workspaceAliases } = require('workspace-alias')
const workspaceAliases = require('workspace-alias')

module.exports = {
  // ...
  plugins: [
    // ...
    alias(workspaceAliases()),
  ],
}

with Jest

const { jest: workspaceAliases } = require('workspace-alias')

module.exports = {
  // ...
  moduleNameMapper: workspaceAliases(),
}

using mainFields option

const { jest: workspaceAliases } = require('workspace-alias')

module.exports = {
  // ...
  moduleNameMapper: workspaceAliases({ mainFields: ['main'] }),
}