Important: This documentation covers Yarn 1 (Classic).
For Yarn 2+ docs and migration guide, see yarnpkg.com.

Package detail

webpack-remove-empty-scripts

webdiscus781.1kISC1.1.1TypeScript support: included

Webpack plugin removes empty JavaScript files generated when using styles.

webpack, plugin, remove, empty, script, entry, style, scss, sass, css, js, javascript

readme

A Webpack plugin to remove empty JavaScript files generated when using style only entries.

Problem this plugin solves

By default, Webpack creates a JavaScript file for every entry specified in the entry option - even when the entry is a style file (like SCSS or CSS).

Example:

module.exports = {
  entry: {
    styles: './styles.scss',
  },
}

Output:

dist/styles.css
dist/styles.js // <= unwanted empty JS file

When using mini-css-extract-plugin, CSS is correctly extracted into a separate file, but Webpack still emits an empty JavaScript file for each style-only entry - the known issue.

This plugin detects and removes those redundant .js files automatically, keeping your output clean.

Note

This plugin is compatible with Webpack 5. For Webpack 4 use webpack-fix-style-only-entries.

Install

npm install webpack-remove-empty-scripts --save-dev

See the full documentation on GitHub.

changelog

1.1.0 (2025-05-25)

  • chore: optimize npm package and reduce unpacked size: 31 kB -> 9 kB
  • docs: update readme

1.0.4 (2023-09-23)

  • docs: update readme

1.0.4 (2023-08-28)

  • fix: remove needless double new lines in console output when the verbose option is enabled
  • chore: add Community Standards files
  • chore: update dev packages
  • test: remove the test strategy for node versions 12.x on GitHub to allows use the latest dev packages. The plugin is still compatible with node 12.x.
  • test: add the test strategies for node versions 18.x and 20.x on GitHub
  • test: refactor test utilities
  • test: add tests for alternative way using the html-bundler-webpack-plugin
  • docs: update readme

1.0.3 (2023-04-11)

  • fix: fix interface syntax in TS
  • fix: options in constructor now is optional parameter in types for TS.

1.0.2 (2023-04-07)

  • fix: correctly export types for TS when used CommonJS
  • chore: update dev packages
  • docs: update readme

1.0.1 (2022-09-19)

  • docs: update readme

1.0.0 (2022-09-12)

  • BREAKING CHANGE: reverted default behavior as in v0.8.1 - remove empty scripts before other plugins will be called. This change is needs for properly work of the vast majority of webpack plugins.

    For compatibility with v0.8.2 - v0.8.4, if you have an issue, use new stage option with the value:

    new RemoveEmptyScriptsPlugin({
  stage: RemoveEmptyScriptsPlugin.STAGE_AFTER_PROCESS_PLUGINS,
})
  • feat: add new stage option. Webpack's plugins use different stages for their functionality. For properly work other plugins can be specified the stage when should be removed empty scripts: before or after processing of other webpack plugins.\ For example, using @wordpress/dependency-extraction-webpack-plugin the empty scripts must be removed after processing all plugins. Using webpack-manifest-plugin the empty scripts must be removed before processing other plugins.
  • chore: update packages
  • test: add the test for using with webpack-manifest-plugin
  • docs: update readme

0.8.4 (2022-09-08)

  • fix: fix last stable version of ansis in package.json to avoid issues in dependency

0.8.3 (2022-09-04)

  • docs: update readme

0.8.2 (2022-09-04)

  • fix: keep extracted wordpress dependencies, #9
  • test: refactor tests
  • chore: update npm packages

0.8.1 (2022-06-14)

  • fix: add supports for TypeScript
  • chore: update packages
  • docs: update readme

0.8.0 (2022-04-01)

  • feat: add new option remove to define custom RegExp for generated assets that must be removed
  • chore: update packages

0.7.3 (2022-01-30)

  • feat: add color verbose output via ANSI color library - ansis
  • feat: add the test case for styles imported from javascript

0.7.2 (2021-12-13)

  • feat: add new option enable to enable / disable the plugin, e.g. by development
  • feat: add supports of RegExp for option extensions
  • chore: remove deprecated option silent, use verbose to show process information (no braking change)
  • chore: add GitHub workflow + codecov
  • chore: update packages
  • docs: update readme

0.7.1 (2021-01-14)

  • fix: the issue infinite recursion by collect of resources from dependency modules by usage in react app some big components with many thousands dependencies

0.7.0 (2020-12-21)

  • chore: deprecate the silent option, it will be removed on Jun 30, 2021. Use option verbose: true to show in console each removed empty file. Defaults, verbose: false.
  • fix: issue Maximum call stack size exceeded in all cases, for example, by usage the webpack setting optimization.concatenateModules: true and:
    • import react
    • import redux
    • webpack setting externals.jquery: 'jQuery' or other external libs
  • fix: the issue if first in webpack entries are a styles and then a scripts

0.6.4 (2020-12-19)

  • feat: improve the option ignore:
    • it can be the array of string or RegExp
    • added default value of ignore as ['/node_modules/'] to ignore resources from node_modules path
  • fix: the error: Maximum call stack size exceeded with webpack setting optimization.concatenateModules: trueand usage in script imports from react and redux
  • test: add the test case for single style without a scripts in webpack config
  • test: add silent mode in tests to suppress output log info in the console
  • chore: update packages

0.6.3 (2020-10-25)

  • fix: BREAKING CHANGE in Webpack 5: no more changes should happen to Compilation.assets
  • refactor: update code according Webpack 5 API

0.6.2 (2020-10-24)

  • chore: update packages

0.6.1 (2020-10-20)

The fork of original webpack-fix-style-only-entries (ver. 0.6.0) for support only Webpack 5 and above. The Webpack 4 is no longer supported.

The changes from original version 0.6.0:

  • feat: considers the use hash after the .js and .mjs extension in file format like .js?[hash] or .mjs?[hash]. The idea and requirement belong to MatiasMorici from PR

  • fix: in Webpack 5 fixed deprecation messages:

    • DEP_WEBPACK_CHUNK_HAS_ENTRY_MODULE
    • DEP_WEBPACK_CHUNK_ENTRY_MODULE
    • DEP_WEBPACK_DEPRECATION_ARRAY_TO_SET
    • DEP_WEBPACK_MODULE_INDEX

  • fix: integration test script for using with Webpack 5

  • fix: issue using terser-webpack-plugin is generated the needless file vendor.js.LICENSE.txt in the production test vendor+multi-js-entry-css-entry
  • docs: corrected module structure in README.md
  • chore: update packages

0.6.0 (Oct 13, 2020)

Being overly careful here, this version is not breaking for almost all the existing users. It could possibly break in some edge cases, since it changes how modules are collected (from global to one each compilation) or if you have a workaround for a working webpack multi configuration.

  • BREAKING POSSIBLY: Use a dedicated cache for every compilation (Prevent arbitrary files deletion when using Webpack with multi configurations) (PR #39)

0.5.2 (Oct 07, 2020)

  • feat: supports Webpack 5 using ModuleGraph API (PR #38)
  • chore: npm audit fix: (ea9dd7)

0.5.1 (Jun 13, 2020)

  • fix: Maximum call stack size exceeded (PR #34)
  • chore: add CHANGELOG (3e3767)

0.5.0 (May 18, 2020)

0.4.0 (Sep 8, 2019)

  • feat: add support for module js files (PR #21)