Package Exports
- hops-middleware
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (hops-middleware) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
Hops Middleware
Hops assumes you will write an Express-style middleware, transpiles it using Webpack and makes it easy to use in non-transpiled and even non-server code. Hops' middleware is a simple helper to simplify using your custom middleware with an Express server.
You can override hops' default Webpack configuration by passing a webpackConfig
object to the createMiddleware
function. You can also enable watch mode by passing a watchOptions
object.
Target Audience
If you want to write your Express middleware in ECMAScript Next, reuse your Webpack loader config and have your stuff transpiled on the fly to use it in your own Express server (or in Webpack Dev Server), hops' middleware is for you.
Example
This example shows how to write and configure a custom middleware and use it in a stock Express server.
package.json
{
...
"server": "src/server.js",
"main": "index.js",
"dependencies": {
"hops-build-config": "*",
"hops-middleware": "*"
}
...
}
src/server.js
export default (req, res) => {
switch (req.url) {
case '/foo':
res.write('hello foo');
break;
case '/bar':
res.write('hello bar');
break;
default:
res.writeHead(404);
res.write('not found');
break;
}
res.end();
};
index.js
const express = require('express');
const createMiddleware = require('hops-middleware');
const webpackConfig = require('hops-build-config').nodeConfig;
const app = express();
app.use(express.static('dist'));
app.all('*', createMiddleware(webpackConfig /*, watchOptions */));
app.listen(3000);
Hops' own renderer is one example of the middleware in action.