Installations

npm install rollup-plugin-livereload-universal

Developer Guide

BETA

Typescript

Yes

Module System

CommonJS

Node Version

13.9.0

NPM Version

6.13.7 Pull Requests

Open

14

Total

15

Closed

1

Issues

Open

0

Total

0

Closed

0

Releases

1

v1.0.0

Updated on Jun 06, 2020

View All 1 releases

Languages

2

TypeScript

JavaScript

TypeScript (62.49%)

JavaScript (37.51%)

Developer

mrnateriver

Download Statistics

Total Downloads

0

Last Day

0

Last Week

0

Last Month

0

Last Year

0

GitHub Statistics

MIT License

2 Commits

1 Forks

1 Watchers

15 Branches

1 Contributors

Updated on Jun 06, 2020

Maintainers

1

View All 1 Contributors

Package Meta Information

Latest Version

1.0.0

Package Id

rollup-plugin-livereload-universal@1.0.0

Unpacked Size

29.64 kB

Size

7.03 kB

File Count

11

NPM Version

6.13.7

Node Version

13.9.0

Total Downloads

Cumulative downloads

Total Downloads

NaN

Last Day

0%

NaN

Compared to previous day

Last Week

0%

NaN

Compared to previous week

Last Month

0%

NaN

Compared to previous month

Last Year

0%

NaN

Compared to previous year

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dependencies

1

livereload

Dev Dependencies

22

Universal Rollup LiveReload Plugin

This plugin allows manually triggering reload of the user's page via LiveReload WS connection. This plugin was conceived as a supplement for rollup-plugin-memory-fs, since it is the only way to provide live reloading while using that plugin. However, as the name implies, it's universal.

This plugin is heavily inspired by and partly taken from rollup-plugin-livereload, so big kudos to Thomas Ghysels for that plugin. If you're not using rollup-plugin-memory-fs, there's a high probability his plugin will work for you just fine.

Installation

# yarn
yarn add -D rollup-plugin-livereload-universal

# npm
npm install --save-dev rollup-plugin-livereload-universal

Usage

1// rollup.config.js
2import serve from 'rollup-plugin-serve';
3import memfs from 'rollup-plugin-memory-fs'
4import livereload from 'rollup-plugin-livereload-universal'
5
6const memfsPlugin = memfs();
7const livereloadPlugin = livereload({ reloadEmitter: memfsPlugin });
8
9export default {
10  input: 'src/main.js',
11  output: {
12    file: 'dist/bundle.js',
13    format: ...
14  },
15  plugins: [
16    serve({ contentBase: ['./dist'] }),
17    memfsPlugin,
18    livereloadPlugin,
19  ]
20}

Options

Option	Type	Required	Default	Description
reloadEmitter	ReloadEmitter	`true`	`undefined`	EventEmitter that emits `reload` event for reloading user's page.
verbosity	`"silent"` \| `"startup"` \| `"debug"` Verbosity	`false`	`"startup"`	Level of output verbosity.
watch	`string`	`false`	`undefined`	A single path or an array of paths that should be watched for changes for reloading the user's page. Accepts both directories and specific files. If not specified, any `reload` event will cause page refresh. If relative path is specified, it's resolved relative to Rollup output directory (or directory in which `output.file` resides; each output is checked).
port	`number`	`false`	`35729`	Port that LiveReload WS server will listen to.
clientUrl	`string`	`false`	`undefined`	URL of a custom client JS script that's supposed to connect to LiveReload WS server.

ReloadEmitter

If you're writing your own emitter (as opposed to using, for example, rollup-plugin-memory-fs), note that you should emit reload event for each file that caused the reload (in case there were several files), so that handler can respect the watch parameter accurately. All emissions of reload events are buffered for the next iteration of Node.js event loop, so it's fine to emit several events simultaneously.

Changelog

Please see CHANGELOG for more information what has changed recently.

Contributing

Contributions and feedback are more than welcome.

To get it running:

Clone the project;
npm install;
npm run build.

Credits

Evgenii Dobrovidov;
Thomas Ghysels for original implementation;
All Contributors.

License

The MIT License (MIT). Please see LICENSE for more information.

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

Maintained

Determines if the project is "actively maintained".

0

SAST

Determines if the project uses static code analysis.

0

Code-Review

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

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

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

Score

1.7

/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