Skip to content

Emurgo/webpack-httpolyglot-server

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

12 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

webpack-httpolyglot-server

Using httpolyglot to serve http/https over the same port for Webpack development server

Why?

The React Chrome Extension Boilerplate need a https webpack server on development mode (Inject page), and we also need http for Window, Popup, Background features, I just don't want to open two webpack servers for that, so I made a tool, provide a easy way to achieve.

Installation

$ npm i --save-dev webpack-hot-middleware
$ npm i --save-dev webpack-httpolyglot-server

Usage

CLI

Not yet.

Node

var createWebpackServer = require('webpack-httpolyglot-server');

const server = createWebpackServer(config, serverOptions);

The config can be Array, it can use multiple config.

Configuration

output.publicPath

Use // as a prefix instead of http:// or https://, but if you're making chrome extension (prefix: chrome-extension://), it's not applicable.

webpack-hot-middleware entry

This tool used webpack-hot-middleware for enable hot module replacement.

devMiddleware

Apply webpack-dev-middleware options.

hotMiddleware

Apply webpack-hot-middleware options.

Credits

License

MIT

About

Using mscdex/httpolyglot to serve http/https over the same port for Webpack development server

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

 
 
 

Contributors

Languages

  • JavaScript 100.0%