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

resolve-entry-modules-webpack-plugin

v2.0.0

Published

Webpack plugin for considering each entry's enclosing directory as a resolve root

Downloads

321

Readme

Resolve Entry Modules Webpack Plugin

Webpack plugin for considering each entry's enclosing directory as a resolve root for all imports within occurring in the dependency tree of that entry. It is effectively the same as defining a resolve.modules for each directory of your entry while ensuring that distinct entries cannot import from the others.

Usage

Imagine the following project structure:

project/
├── entry-one/
│   ├── index.js
│   └── a.js
└── entry-two/
    ├── index.js
    └── a.js

For each entry point, we'd like to import a.js directly (without relative paths):

var a = require( 'a' );

To enable this, we can simply include ResolveEntryModulesPlugin as a plugin in our Webpack configuration:

// webpack.config.js
const ResolveEntryModulesPlugin = require( 'resolve-entry-modules-webpack-plugin' );

module.exports = {
	entry: {
		one: './entry-one/index.js',
		two: './entry-two/index.js'
	},
	plugins: [
		new ResolveEntryModulesPlugin()
	]
};

License

Copyright 2018 Andrew Duthie

Released under the MIT License.