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

package-extend-resolver-plugin

v0.0.5

Published

Let's you have one parent workspace and multiple child workspaces that override only specific modules (styles, assets, etc.) of the parent. That way having a main web application, you can easily adapt it to different platforms by creating child workspaces

Downloads

3

Readme

PackageExtendResolverPlugin

Let's you have one parent workspace and multiple child workspaces that override only specific modules (styles, assets, etc.) of the parent. That way having a main web application, you can easily adapt it to different platforms by creating child workspaces with only overrides to specific modules inside. This keeps your project clean and organized.

Quick start

Note: If you are using bundlewiz, you do not need to include this plugin yourself as bundlewiz does it for you. Otherwise follow the steps below.

const PackageExtendResolverPlugin = require('package-extend-resolver-plugin');

    // ...
    plugins: [
        // ...
        new PackageExtendResolverPlugin()
    ]
    // ...

If you do not use .jsx (or other fancy extensions) on the modules that you import without explicitly specifying an extension (e.g import SomeComponent from 'components/SomeComponent when you really mean SomeComponent.jsx) and keep all of your modules, and styles and other assets (like images, fonts, etc.) that you import in your modules under the src/ folder, you do not need to provide any options!

Options

  • lookIn string[] = [ 'src' ] - array of paths to look up the modules (if path is relative, workspace root will be prepended to it, node_modules will be looked up automatically)
  • assumeExtensions string[] = [] - array of additional extensions that you are looking to omit when importing the corresponding modules (e.g. to properly resolve .jsx files, you need to add .jsx to the array)

Example

const PackageExtendResolverPlugin = require('package-extend-resolver-plugin');

    // ...
    plugins: [
        // ...
        new PackageExtendResolverPlugin({
            lookIn: [ 'src' ], // default
            assumeExtensions: [ '.jsx' ] // now you can include JSX Components without specifying an extension
        })
    ]
    // ...