npmpackage.info

Gathering detailed insights and metrics for @gem-mine/rollup-plugin-rename-node-modules

@gem-mine/rollup-plugin-rename-node-modules - 1.0.1 | npmpackage.info

@gem-mine/rollup-plugin-rename-node-modules

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

1.0.1

MIT

TypeScript

10.60 kB

2.3

Installations

npm install @gem-mine/rollup-plugin-rename-node-modules

Developer Guide

BETA

Typescript

Yes

Module System

CommonJS

Node Version

14.15.1

NPM Version

7.5.4 Pull Requests

Open

1

Total

6

Closed

0

Merged

5

Issues

Open

2

Total

5

Closed

3

Releases

1.3.1

v1.3.1

Updated on Jan 12, 2022

1.3.0

v1.3.0

Updated on Jan 08, 2022

1.2.0

Updated on Sep 13, 2021

1.1.0

Updated on Mar 15, 2021

View All 4 releases

Languages

TypeScript

JavaScript

TypeScript (90.54%)

JavaScript (9.46%)

Developer

Lazyuki

Download Statistics

Total Downloads

Last Day

Last Week

Last Month

Last Year

GitHub Statistics

MIT License

23 Stars

24 Commits

10 Forks

2 Watchers

1 Branches

5 Contributors

Updated on Feb 10, 2025

Maintainers

View All 5 Contributors

Package Meta Information

Latest Version

1.0.1

Package Id

@gem-mine/rollup-plugin-rename-node-modules@1.0.1

Unpacked Size

10.60 kB

Size

3.13 kB

File Count

NPM Version

7.5.4

Node Version

14.15.1

Total Downloads

Cumulative downloads

Total Downloads

NaN

Last Day

NaN

Compared to previous day

Last Week

NaN

Compared to previous week

Last Month

NaN

Compared to previous month

Last Year

NaN

Compared to previous year

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dependencies

estree-walker magic-string

Dev Dependencies

husky prettier pretty-quick rimraf rollup rollup-plugin-typescript2 tslib typescript

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:

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

Usage

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

1import renameNodeModules from "rollup-plugin-rename-node-modules";
2
3export default {
4  input: "src/index.js",
5  output: {
6    dir: "output",
7    format: "cjs",
8  },
9  plugins: [renameNodeModules("ext")],
10};

It takes a string and will rename files and mentions of node_module to the provided string. By default it's external.

Credit

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

No vulnerabilities found.

10

Binary-Artifacts

Determines if the project has generated executable (binary) artifacts in the source repository.

10

License

Determines if the project has defined a license.

2

Code-Review

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

2

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

0

Maintained

Determines if the project is "actively maintained".

0

CII-Best-Practices

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

0

Security-Policy

Determines if the project has published a security policy.

0

Fuzzing

Determines if the project uses fuzzing.

0

Branch-Protection

Determines if the default and release branches are protected with GitHub's branch protection settings.

0

SAST

Determines if the project uses static code analysis.

Score

2.3

/10

Last Scanned on 2025-07-07

The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.

Learn More