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-shimify

v1.0.0

Published

custom resolve for browserify

Downloads

11

Readme

resolve-shimify

Custom resolve for browserify.

Here are two typical cases where this plugin comes in handy:

  1. Make require('react') equal to require('react/dist/react.js'), even for react components installed in node_modules, most of them not specifying a browser-filed in package.json
  2. Make symlinks resolved to their real paths, so that they can be treated as local packages and transforms from package.json may be applicable. You can use realpathify, which is based on this plugin.

This plugin hacks a private property of the browserify instance (b._bresolve). It does not transform file contents, but makes twists to the behaviour of resolving the module paths. So it is much more faster than applying a global transform.

Usage

var browserify = require('browserify');
var shimify = require('resolve-shimify');

browserify(opts)
.plugin(shimify, { react: 'react/dist/react.js' })
;

b.plugin(shimify, shimFn)

shimFn(module)

Type: Function

Return: String, undefined

This function is called before resolving, to transform module to some other value to resolve.

If the returned value is falsy, the original module value will be used.

b.plugin(shimify, shims)

shims

Type: Object

A map for transforming module.

Each key must be either an absolute path or a module path.