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

@bva/override-resolver

v0.1.0

Published

Webpack resolver plugin for overriding or aliasing dependencies and component requests.

Downloads

2

Readme

Override Resolver

Webpack resolver plugin for overriding or aliasing dependencies and component requests.

Leverages enhanced-resolve to handle internal resolution and hook into the request’s lifecycle.

Installation

//npm
npm install @bva/override-resolver

//yarn
yarn add @bva/override-resolver

Why?

This plugin was born from the need to customize 3rd party UI Kits, Component Libraries, etc. without requiring a local clone of the entire library.

A simple example is a Button component provided by a library installed in node_modules as a dependency. This **Button** may be in use by said library throughout multiple other components, which typically makes it difficult to add global custom logic to that Button across your app or project.

Override Resolver trivializes such scenario by providing the option to update that one Button component, or specific parts of it, without affecting the rest of the Component Library.

Why not use Webpack’s native resolve.modules or resolve.alias?

Both of those may be good enough for certain applications, however they share the limitation of not resolving a package’s internal relative requests. Webpack resolve.modules and resolve.alias would only work if all requests were done using module paths (i.e. @moduleName/path/to/component).

Override Resolver is able to handle absolute, module, and relative paths. If a request to a file exists, Override Resolver is able to override it.

Other applications

This plugin can be used outside of simple Component/UI Library overrides you can specify any given request path to alias or override files from.

This can also be leveraged to setup a theme structure or a fallback system for your modules and components.

Support

Requires Webpack 4.x+ and works with NuxtJS, Vue, NextJS, React, JS, SCSS, plus any other file type or framework that can use Webpack.

Usage

Webpack Config file

const path = require('path');
const OverrideResolver = require('@bva/override-resolver');

const WebpackConfig = {
  //...
  resolve: {
    plugins: [
      new OverrideResolver({
        name: '@bva',
        alias: path.resolve(__dirname, 'overrides'),
      })
    ],
  },
  //...
}

module.exports = WebpackConfig;

NuxtJS

import path from 'path';
import OverrideResolver from '@bva/override-resolver';

const NuxtConfig = {
  //...
  build: {
    extend(config) {
      config.resolve.plugins.push(new OverrideResolver(
        {
          name: '@bva',
          alias: path.resolve(__dirname, 'overrides'),
        },
      ));
    },
  },
  //...
};

export default NuxtConfig;