Question 1

How do I set up webpack-extension-reloader for multiple content scripts?

Accepted Answer

Configure the entries.contentScript option as an array in the plugin settings, like ['my-first-content-script', 'my-second-content-script'], as shown in the README's multiple entry support section.

Question 2

Does webpack-extension-reloader work with Firefox add-ons?

Accepted Answer

Yes, it supports all WebExtensions-compatible browsers, including Firefox, by using the standard browser runtime API for reloading, as mentioned in the multi-browser support feature.

Question 3

webpack-extension-reloader vs manual reloading: is it worth it?

Accepted Answer

It automates the reload process after each code change, significantly speeding up development by eliminating the need to manually click reload in the browser, as evidenced by the time-saving workflow described.

Question 4

How to use the CLI without installing anything globally?

Accepted Answer

Run npx webpack-extension-reloader with optional flags like --config and --port, as detailed in the CLI section, allowing quick testing without permanent setup.

Question 5

Can I use this with React or Vue in my extension?

Accepted Answer

Yes, but note that without HMR, state won't persist on reload; it only triggers a full extension reload when Webpack recompiles, so you'll lose component state during development.

Question 6

webpack-extension-reloader or webpack-hot-middleware for extensions?

Accepted Answer

Webpack Extension Reloader is specifically designed for browser extensions and uses the browser API, while webpack-hot-middleware is for web apps and may not handle extension contexts properly, making this plugin the better choice for extension development.

webpack-extension-reloader

What is webpack-extension-reloader?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions