Installations

npm install @kooneko/livereload-webpack-plugin

Developer Guide

BETA

Typescript

No

Module System

CommonJS

Node Version

14.15.4

NPM Version

6.14.10 Score

46.1

Supply Chain

68.1

Quality

72.5

Maintenance

100

Vulnerability

99.3

License

Pull Requests

Open

0

Total

1

Closed

0

Merged

1

Issues

Open

0

Total

1

Closed

1

Releases

3

v1.2.1

Published on 16 Jan 2021

v1.2.0

Published on 25 Oct 2020

First release

v1.1.0

Published on 25 Oct 2020

View all 3 releases

Contributors

1

Unable to fetch Contributors

View all 1 contributors

Languages

1

JavaScript

JavaScript (100%)

Developer

Kooneko

Download Statistics

Total Downloads

191,886

Last Day

89

Last Week

827

Last Month

5,125

Last Year

46,997

GitHub Statistics

5 Stars

16 Commits

1 Forks

2 Watching

1 Branches

1 Contributors

Maintainers

1

Package Meta Information

Latest Version

1.2.1

Package Id

@kooneko/livereload-webpack-plugin@1.2.1

Unpacked Size

22.07 kB

Size

6.82 kB

File Count

16

NPM Version

6.14.10

Node Version

14.15.4

Total Downloads

Cumulative downloads

Total Downloads

191,886

Last day

-68%

89

Compared to previous day

Last week

-28.6%

827

Compared to previous week

Last month

-2.4%

5,125

Compared to previous month

Last year

-17.7%

46,997

Compared to previous year

Daily Downloads

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dependencies

5

anymatch get-port tiny-lr webpack webpack-cli

Dev Dependencies

1

jest

Versions

livereload-webpack-plugin

This plugin for Webpack is based from statianzo's plugin : webpack-livereload-plugin
This plugin is compatible wih Webpack 4 & Webpack 5

Installation

Install the package

1npm install --save-dev @kooneko/livereload-webpack-plugin

Add the plugin to your webpack config

1// webpack.config.js
2
3var LiveReloadWebpackPlugin = require('@kooneko/livereload-webpack-plugin');
4
5module.exports = {
6  plugins: [
7    new LiveReloadWebpackPlugin(options)
8  ]
9}

Add a script tag to your page pointed at the livereload server

1<script src="http://localhost:35729/livereload.js"></script>

Options

Option	Default	Description
`protocol`	protocol of the page, either `http` or `https`	Protocol for livereload `<script>` src attribute value
`port`	`35729`	The desired port for the livereload server. If you not define port, an available port will be searched for, starting from 35729
`hostname`	hostname of the page, like `localhost` or `10.0.2.2`	The desired hostname for the appended `<script>` (if present) to point to
`quiet`	`false`	Prevent message " Live reload listening on port ..." from appearing in the console
`appendScript`	`false`	Append livereload `<script>` automatically to `<head>`
`delay`	`0`	amount of milliseconds by which to delay the live reload (in case build takes longer)
`ignore`	`null`	RegExp of files to ignore. Null value means ignore nothing. It is also possible to define an array and use multiple anymatch patterns

Why?

Yes, there's already webpack-dev-server that handles live reloading and more complex scenarios. This project aims to solve the case where you want assets served by your app server, but still want reloads triggered from webpack's build pipeline.

HTTPS

If you set key, cert, or pfx options, they'll get passed through to tiny-lr as options and it will serve over HTTPS. You'll also also set protocol to https.

FAQ

Webpack always generates js and css together

If this slows your build process you could set liveCSS and liveImg to false to prevent multiple reloads.

No vulnerabilities found.

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.

0

Code-Review

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

0

Maintained

Determines if the project is "actively maintained".

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.

0

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

Score

1.7

/10

Last Scanned on 2024-12-23

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