Installations

npm install rollup-plugin-rebase

Pull Requests

Open

9

Total

27

Closed

13

Merged

5

Issues

Open

5

Total

29

Closed

24

Releases

112

Release 4.1.1

4.1.1

Published on 22 Mar 2022

Release 4.0.3

4.0.3

Published on 22 Mar 2022

Release 4.0.2

4.0.2

Published on 02 Mar 2022

Release 4.0.1

4.0.1

Published on 20 Jan 2022

Release 4.0.0

4.0.0

Published on 19 Jan 2022

Release 3.6.9

3.6.9

Published on 22 Jul 2021

View all 112 releases

Developer

sebastian-software

Developer Guide

BETA

Module System

CommonJS

Min. Node Version

>=14

Typescript Support

No

Node Version

16.14.2

NPM Version

8.5.0 Statistics

59 Stars

499 Commits

12 Forks

5 Watching

8 Branches

4 Contributors

Updated on 15 Jul 2024

Bundle Size

398.81 kB

Minified

105.12 kB

Minified + Gzipped

Bundlephobia

Languages

JavaScript (96.31%)

CSS (2.38%)

SCSS (1.31%)

Total Downloads

Cumulative downloads

Total Downloads

405,653

Last day

-3.6%

295

Compared to previous day

Last week

43.4%

3,091

Compared to previous week

Last month

-31.4%

10,123

Compared to previous month

Last year

128.4%

61,325

Compared to previous year

Daily Downloads

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dependencies

10

@rollup/pluginutils asset-hash core-js fs-extra postcss postcss-import postcss-sass postcss-scss postcss-smart-asset sugarss

Dev Dependencies

16

@babel/core @babel/plugin-transform-runtime @babel/preset-env @effective/eslint-config @effective/prettier babel-core babel-jest eslint jest preppy prettier release-it rimraf rollup semver typescript

Versions

Rollup Rebase

The Rollup Rebase Plugin copies static assets as required from your JavaScript code to the destination folder and adjusts the references in there to point to the new location. It also respects assets referenced from your CSS/SCSS files.

Features

Copies over asset files references from JavaScript into the given output folder.
Adjust asset references in the output JavaScript files to map to the relative new location.
Transforms CSS files to inline all includes from @import via PostCSS Import into the origin files.
Detects and processes assets referenced from both, JavaScript and CSS.
Renames all assets based on their hash (XXHash + Base62) so that conflicts are automatically eliminated while producing a flat output structure.
Supports normal CSS, but also SugarSS, SCSS and Sass via the standard PostCSS parser plugins.

Comparison

The plugin is meant as a tool for preparing a library for being published. In this it differs from plugins like Rollup URL Plugin as it is designed for usage in libraries and not for applications. The output of this plugin can be used by tools like Webpacks File Loader, URL Loader or the already mentioned Rollup URL Plugin.

Installation

1$ npm install --save-dev rollup-plugin-rebase

or

1$ yarn add --dev rollup-plugin-rebase

Usage

You can configure Rollup Rebase as part of your Rollup configuration. This can be either done in a rollup.config.js or by scripting using the Rollup API:

1import { rollup } from "rollup"
2import rebasePlugin from "rollup-plugin-rebase"
3
4async function config() {
5  const bundle = await rollup({
6    input: "./src/index.js",
7    plugins: [rebasePlugin()]
8  })
9
10  await bundle.write({
11    dest: "./lib/index.js"
12  })
13}
14
15config()

Options (all optional)

assetFolder: When set assets are placed inside a sub folder with that name.
keepName: If true, generated filenames will be ${filename}~${hash}.${ext} instead of just ${hash}.${ext}
verbose: If true, increases log level
include: Standard include option for rollup plugins.
exclude: Standard exclude option for rollup plugins.

Copyright

No vulnerabilities found.

10

Dangerous-Workflow

Determines if the project's GitHub Action workflows avoid dangerous patterns.

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.

3

Pinned-Dependencies

Determines if the project has declared and pinned the dependencies of its build process.

0

Code-Review

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

0

SAST

Determines if the project uses static code analysis.

0

Maintained

Determines if the project is "actively maintained".

0

Token-Permissions

Determines if the project's workflows follow the principle of least privilege.

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

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

Score

2.7

/10

Last Scanned on 2024-11-18

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