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

rollup-plugin-rename-node-modules

v1.3.1

Published

A Rollup plugin to rename the `node_modules` created when bundling some external libries while using preserveModules

Downloads

18,002

Readme

rollup-plugin-rename-node-modules

🍣 A Rollup plugin to rename the node_modules created when bundling some external libries while using preserveModules

Why?

When you enable preserveModules but also want to bundle some stuff from dependencies (in my case it was css files so that Next.js can use my library), rollup will put the files under node_modules folder under your output dir. This works locally just fine, but if you try to npm publish this output dir, npm will automatically ignore node_modules inside the output dir so your package will not work when distributed through npm. I don't know if this is a bug or a desired behavior, but this plugin fixes this by renaming the node_modules folder to something else and also check each file and rename any relative imports pointing to this node_modules to the corrected path.

Requirements

This plugin requires an LTS Node version (v8.0.0+) and Rollup

Install

Using npm:

npm install rollup-plugin-rename-node-modules --save-dev

Usage

Create a rollup.config.js configuration file and import the plugin:

import renameNodeModules from "rollup-plugin-rename-node-modules";

export default {
  input: "src/index.js",
  output: {
    dir: "output",
    format: "cjs",
  },
  plugins: [renameNodeModules("ext")],
};

It takes a string and will rename files and mentions of node_module to the provided string. By default it's external. Since v1.3.0, you can also pass in a function that takes a string and returns a string.

It has an optional second parameter sourceMap which defaults to true and can disable source map generation:

plugins: [renameNodeModules("ext", false)]

Credit

Base idea taken from https://github.com/GiG/rollup-plugin-rename-extensions