Gathering detailed insights and metrics for webpack-livereload-plugin
Gathering detailed insights and metrics for webpack-livereload-plugin
LiveReload during webpack --watch
Installations
npm install webpack-livereload-pluginReleases
Unable to fetch releases
Developer
statianzo
Developer Guide
BETA
Module System
CommonJS
Min. Node Version
>= 10.18.0
Typescript Support
No
Node Version
12.21.0
NPM Version
6.14.11
Statistics
203 Stars
96 Commits
51 Forks
11 Watching
8 Branches
21 Contributors
Updated on 19 Oct 2024
Bundle Size
341.72 kB
Minified
103.32 kB
Minified + Gzipped
Languages
JavaScript (100%)
Total Downloads
Cumulative downloads
Total Downloads
18,105,978
Last day
3.9%
14,843
Compared to previous day
Last week
12.2%
78,217
Compared to previous week
Last month
24.8%
319,741
Compared to previous month
Last year
20.3%
3,395,059
Compared to previous year
Daily Downloads
Weekly Downloads
Monthly Downloads
Yearly Downloads
Dependencies
4
Peer Dependencies
1
Dev Dependencies
5
Versions
webpack-livereload-plugin
LiveReload when running webpack --watch
Installation
Install the package
1npm install --save-dev webpack-livereload-plugin
Add the plugin to your webpack config
1// webpack.config.js 2 3var LiveReloadPlugin = require('webpack-livereload-plugin'); 4 5module.exports = { 6 plugins: [ 7 new LiveReloadPlugin(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
protocol- (Default: protocol of the page, eitherhttporhttps) Protocol for livereload<script>src attribute valueport- (Default: 35729) The desired port for the livereload server. If you define port 0, an available port will be searched for, starting from 35729.hostname- (Default: hostname of the page, likelocalhostor10.0.2.2) The desired hostname for the appended<script>(if present) to point toappendScriptTag- (Default: false) Append livereload<script>automatically to<head>.ignore- (Default:null) RegExp of files to ignore. Null value means ignore nothing. It is also possible to define an array and use multiple anymatch patterns.delay- (Default:0) amount of milliseconds by which to delay the live reload (in case build takes longer)useSourceHash- (Default:false) create hash for each file source and only notify livereload if hash has changeduseSourceSize- (Default:false) check size for each file source and only notify livereload if size has changed (Faster thanuseSourceHashbut it has a downside. If file size hasn't changed no reload is triggered. For example if color has changed from#000000to#ffffffno reload will be triggered!)
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 your webpack is always generating js and css files together you could set
useSourceHash to true to generate a hash for each changed asset and it
should prevent multiple reloads.
Alternatively if this slows your build process you could set liveCSS
and liveImg to false to prevent multiple reloads.
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
no dangerous workflow patterns detected
Reason
license file detected
Details
- Info: project has a license file: LICENSE:0
- Info: FSF or OSI recognized license: ISC License: LICENSE:0
Reason
Found 6/23 approved changesets -- score normalized to 2
Reason
detected GitHub workflow tokens with excessive permissions
Details
- Warn: no topLevel permission defined: .github/workflows/ci.yml:1
- Info: no jobLevel write permissions found
Reason
0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Reason
dependency not pinned by hash detected -- score normalized to 0
Details
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:16: update your workflow using https://app.stepsecurity.io/secureworkflow/statianzo/webpack-livereload-plugin/ci.yml/master?enable=pin
- Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/ci.yml:17: update your workflow using https://app.stepsecurity.io/secureworkflow/statianzo/webpack-livereload-plugin/ci.yml/master?enable=pin
- Warn: npmCommand not pinned by hash: .github/workflows/ci.yml:21
- Info: 0 out of 2 GitHub-owned GitHubAction dependencies pinned
- Info: 0 out of 1 npmCommand dependencies pinned
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
security policy file not detected
Details
- Warn: no security policy file detected
- Warn: no security file to analyze
- Warn: no security file to analyze
- Warn: no security file to analyze
Reason
project is not fuzzed
Details
- Warn: no fuzzer integrations found
Reason
branch protection not enabled on development/release branches
Details
- Warn: branch protection not enabled for branch 'master'
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
- Warn: 0 commits out of 14 are checked with a SAST tool
Reason
10 existing vulnerabilities detected
Details
- Warn: Project is vulnerable to: GHSA-w8qv-6jwh-64r5
- Warn: Project is vulnerable to: GHSA-3xgq-45jj-v275
- Warn: Project is vulnerable to: GHSA-43f8-2h32-f4cj
- Warn: Project is vulnerable to: GHSA-f8q6-p94x-37v3
- Warn: Project is vulnerable to: GHSA-vh95-rmgr-6w4m / GHSA-xvch-5gv4-984h
- Warn: Project is vulnerable to: GHSA-c2qf-rxjj-qqgw
- Warn: Project is vulnerable to: GHSA-4wf5-vphf-c2xc
- Warn: Project is vulnerable to: GHSA-7p7h-4mm5-852v
- Warn: Project is vulnerable to: GHSA-hc6q-2mpp-qw7j
- Warn: Project is vulnerable to: GHSA-4vvj-4cpr-p986
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