npmpackage.info

Gathering detailed insights and metrics for run-script-webpack-plugin

Other packages similar to run-script-webpack-plugin

webpack-shell-plugin

0.5.0

Run shell commands before and after webpack builds

webpack-shell-plugin-next

2.3.2

Run shell commands before and after webpack builds

webpack-hook-plugin

1.0.7

Run shell commands before and after webpack builds

start-server-webpack-plugin-2

2.1.3

Automatically run your script once Webpack's build completes.

Gathering detailed insights and metrics for run-script-webpack-plugin

run-script-webpack-plugin - 0.2.3 | npmpackage.info

run-script-webpack-plugin

Automatically run your script once Webpack's build completes.

0.2.3

MIT

TypeScript

9.70 kB

4.2

Installations

npm install run-script-webpack-plugin

Developer Guide

BETA

Typescript

Yes

Module System

CommonJS

Min. Node Version

>=14

Node Version

18.20.7

NPM Version

10.8.2 Pull Requests

Open

5

Total

31

Closed

2

Merged

24

Issues

Open

5

Total

12

Closed

7

Releases

Unable to fetch releases

Languages

TypeScript

TypeScript (100%)

Developer

atassis

Download Statistics

Total Downloads

Last Day

Last Week

Last Month

Last Year

GitHub Statistics

MIT License

42 Stars

67 Commits

11 Forks

3 Watchers

5 Branches

11 Contributors

Updated on Jul 03, 2025

Maintainers

View All 11 Contributors

Package Meta Information

Latest Version

0.2.3

Package Id

run-script-webpack-plugin@0.2.3

Unpacked Size

9.70 kB

Size

3.86 kB

File Count

NPM Version

10.8.2

Node Version

18.20.7

Published on

Apr 06, 2025

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

Dev Dependencies

@types/node @typescript-eslint/eslint-plugin @typescript-eslint/parser eslint eslint-config-prettier prettier typescript webpack

run-script-webpack-plugin

Automatically run your script once Webpack's build completes.

NOTE: mostly copied from this repo, but strongly typed from scratch

Installation

1npm i -D run-script-webpack-plugin

Usage

In webpack.config.ts:

1import { RunScriptWebpackPlugin } from "run-script-webpack-plugin";
2
3export default {
4  plugins: [
5    ...
6    // Only use this in DEVELOPMENT
7    new RunScriptWebpackPlugin({
8      name: 'server.js',
9      nodeArgs: ['--inspect'], // allow debugging
10      args: ['scriptArgument1', 'scriptArgument2'], // pass args to script
11      autoRestart: true | false, // Should the script auto-restart after emit. Defaults to true. This should be set to false if using HMR
12      signal: false | true | 'SIGUSR2', // signal to send for HMR (defaults to `false`, uses 'SIGUSR2' if `true`)
13      keyboard: true | false, // Allow typing 'rs' to restart the server. default: only if NODE_ENV is 'development'
14      cwd: undefined | string, // set a current working directory for the child process default: current cwd
15    }),
16  ],
17}

The name argument in RunScriptWebpackPluginOptions refers to the built asset, which is named by the output options of webpack (in the example the entry server becomes server.js. This way, the plugin knows which entry to start in case there are several.

If you don't pass a name, the plugin will tell you the available names.

You can use nodeArgs and args to pass arguments to node and your script, respectively. For example, you can use this to use the node debugger.

To use Hot Module Reloading with your server code, set Webpack to "hot" mode and include the webpack/hot/poll or webpack/hot/signal modules. Make sure they are part of your server bundle, e.g. if you are using node-externals put them in your whitelist. The latter module requires the signal option.

License

Refer to LICENSE file

Contributing

Use conventional commmits
There is a eslint config in the repo. Check if no new errors are added. (dont change the config inside ur PRs)

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.

10

Packaging

Determines if the project is published as a package that others can easily download, install, easily update, and uninstall.

6

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

4

Maintained

Determines if the project is "actively maintained".

3

Code-Review

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

2

Pinned-Dependencies

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

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

SAST

Determines if the project uses static code analysis.

Score

4.2

/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