Skip to content

Reduce disk impact of Rollup NPM package #4076

@TimvdLippe

Description

@TimvdLippe

Expected Behavior / Situation

Rollup should have a minimal disk impact in node_modules

Actual Behavior / Situation

Rollup takes up 4.3MB of disk space in the node_modules/ of Chrome DevTools, which puts it in the top 10 largest packages.

988K	node_modules/rollup/dist/shared
364K	node_modules/rollup/dist/rollup.browser.js
 72K	node_modules/rollup/dist/bin
 24K	node_modules/rollup/dist/rollup.d.ts
4.0K	node_modules/rollup/dist/rollup.js
4.0K	node_modules/rollup/dist/loadConfigFile.js
1.3M	node_modules/rollup/dist/rollup.browser.js.map
1.3M	node_modules/rollup/dist/es

Rollup ships with a sourcemap that takes up 30% of its bundle.

Modification Proposal

Similarly to what we have done with Acorn (acornjs/acorn#1023) and ESLint (eslint/eslint#14098), can we remove the sourcemap from the NPM package?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions