rollup-plugin-node-globals

v1.4.0

insert the same globals browserify does

NPM

README

GitHub

Website

MIT

Latest version published 3 years ago

    npm install rollup-plugin-node-globals

We couldn't find any similar packages Browse all packages

Package Health Score

53 / 100

Popularity
Recognized
Maintenance
Inactive
Security
No known security issues
Community
Sustainable

Make sure the open source you're using is safe to use

Secure my Project

Popularity

Recognized

Weekly Downloads (60,838)

Dependents: 2.21K
GitHub Stars: 80
Forks: 17
Contributors: 5

The npm package rollup-plugin-node-globals receives a total of 60,838 downloads a week. As such, we scored rollup-plugin-node-globals popularity level to be Recognized.

Based on project statistics from the GitHub repository for the npm package rollup-plugin-node-globals, we found that it has been starred 80 times, and that 2,212 other projects in the ecosystem are dependent on it.

Downloads are calculated as moving averages for a period of the last 12 months, excluding weekends and known missing data points.

Security

No known security issues

Security and license risk for significant versions

All Versions

Direct Vulnerabilities

1.0.9

1.1.0

1.2.1

1.3.0

1.4.0

Indirect Vulnerabilities

1.0.9

1.1.0

1.2.1

1.3.0

1.4.0

License Risks

1.0.9

1.1.0

1.2.1

1.3.0

1.4.0

All security vulnerabilities belong to production dependencies of direct and indirect packages.

License

MIT

Security Policy

We found a way for you to contribute to the project! Looks like rollup-plugin-node-globals is missing a security policy.

You can connect your project's repository to Snyk to stay up to date on security alerts and receive automatic fix pull requests.

    # Install the Snyk CLI and test your project
npm i snyk -g && snyk test rollup-plugin-node-globals

Keep your project free of vulnerabilities with Snyk

Maintenance

Inactive

Commit Frequency

No Recent Commits

Open Issues: 11
Open PR: 15
Last Release: 3 years ago
Last Commit: 3 years ago

Further analysis of the maintenance status of rollup-plugin-node-globals based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Inactive.

An important project maintenance signal to consider for rollup-plugin-node-globals is that it hasn't seen any new versions released to npm in the past 12 months, and could be considered as a discontinued project, or that which receives low attention from its maintainers.

As a healthy sign for on-going project maintenance, we found that the GitHub repository had at least 1 pull request or issue interacted with by the community.

Community

Sustainable

Readme.md: Yes
Contributing.md: No
Code of Conduct: No
Contributors: 5
Funding: No

This project has seen only 10 or less contributors.

We found a way for you to contribute to the project! Looks like rollup-plugin-node-globals is missing a Code of Conduct.

Embed Package Health Score Badge

Package

Node.js Compatibility: not defined

Age: 5 years
Dependencies: 6 Direct
Versions: 16
Install Size: 29.6 kB
Dist-tags: 1
# of Files: 9
Maintainers: 1
TS Typings: Yes

rollup-plugin-node-globals has more than a single and default latest tag published for the npm package. This means, there may be other tags available for this package, such as next to indicate future releases, or stable to indicate stable releases.

rollup-plugin-node-globals

Plugin to insert node globals including so code that works with browserify should work even if it uses process or buffers. This is based on rollup-plugin-inject .

process
global
Buffer
__dirname
__filename

Plus process.nextTick and process.browser are optimized to only pull in themselves and __dirname and __filename point to the file on disk

There are a few options to control output

process - pass false to disable process polyfilling
global - pass false to disable global polyfilling
buffer - pass false to disable Buffer polyfilling
dirname - pass false to disable __dirname polyfilling
filename - pass false to disable __filename polyfilling
baseDir which is used for resolving __dirname and __filename.

examples

var foo;
if (process.browser) {
  foo = 'bar';
} else {
  foo = 'baz';
}

turns into

import {browser} from 'path/to/process';
var foo;
if (browser) {
  foo = 'bar';
} else {
  foo = 'baz';
}

but with rollup that ends up being

var browser = true;
var foo;
if (browser) {
  foo = 'bar';
} else {
  foo = 'baz';
}

var timeout;
if (global.setImmediate) {
  timeout = global.setImmediate;
} else {
  timeout = global.setTimeout;
}
export default timeout;

turns into

import {_global} from 'path/to/global.js';
var timeout;
if (_global.setImmediate) {
  timeout = _global.setImmediate;
} else {
  timeout = _global.setTimeout;
}
export default timeout;

which rollup turns into

var _global = typeof global !== "undefined" ? global :
            typeof self !== "undefined" ? self :
            typeof window !== "undefined" ? window : {}

var timeout;
if (_global.setImmediate) {
  timeout = _global.setImmediate;
} else {
  timeout = _global.setTimeout;
}
var timeout$1 = timeout;

export default timeout$1;

With that top piece only showing up once no matter how many times global was used.