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 🙏

© 2026 – Pkg Stats / Ryan Hefner

webpack-relative-aliases

v1.0.3

Published

solving webpack overwritten relative aliases

Readme

WebpackRelativeAliases - Plugin

Webpack by default does not support overwriting relative paths, then, WebpackRelativeAliases was designed overwrite relative paths whenever the application is compiling.

Just in case you are using webpack 2.x, you should use webpack2-relative-aliases instead.


plugins: [
   new WebpackRelativeAliases({
       relativeAliases: {
           // simple relative overwrite
           './example.js': '/full/path/to/your/file.js',
           
           // example of file considering the context 
           './example.js': {
               fromContext: 'specific/path/you/want/to/overwrite',
               alias: '/full/path/to/your/file.js'
           },
           // example of module considering the context
           './../example': {
               fromContext: 'specific/path/you/want/to/overwrite',
               alias: '/full/path/to/your/module/'
           },
      },
      debug: true
  })
]

Configuration

The object relativeAliases should be composed by relative aliases that you want to overwrite. It's allow you to set a key value: alias and new path respectfully.

First of all install node module:

$ npm install webpack-relative-aliases --save-dev

Add In your webpack.config.js the following script and then start create an instance of WebpackRelativeAliases setting your own relative aliases.

const WebpackRelativeAliases = require('webpack-relative-aliases');

relativeAliases

Let's suppouse that you want to overwrite ./index.js: /your/new/path/index.js, webpack-relative-aliases then, will search all entrances of ./index.js and overwrite to /your/new/path/index.js

debug

The debug mode has an output message or all aliases that has been matched and overwritten

Examples

Simple reference

plugins: [
    new WebpackRelativeAliases({
        relativeAliases: {
            './example.js': '/full/path/to/your/file.js',
        },
        debug: true
    })
]

Reference minding the context

That might be a rude problem when in your application you probably will have a few aliases likewise the given example, In order to avoid this problem, you may have to consider also what is the context or file structure where this relative path is hosted as shown below:

plugins: [
    new WebpackRelativeAliases({
        relativeAliases: {
            './index.js': {
                fromContext: 'specific/path/you/want/to/overwrite',
                alias: '/your/new/path/index.js'
            }
        },
        debug: true
    })
]

In this case, the alias ./index.js is considered to overwrite when the context matchs with fromContext property, so, you ensure that it's overwriting only in this case and not in the entire application.