fluture-express
fluture-express
npm i fluture-express
fluture-express

fluture-express

🚂 Create Express middleware using Futures

by fluture-js

6.0.1 (see all)License:MITTypeScript:Not Found
npm i fluture-express
Readme

Fluture Express

NPM Version Dependencies Code Coverage

Create Express middleware using Futures from Fluture.

Allows for the definition of pure functions to be used as Express middleware. This has benefits for testing and developer sanity. Another benefit of this particular approach, where every middleware is wrapped individually, is that it plays nicely with existing Express middleware, and they can be used interchangably.

Usage

Node

$ npm install --save fluture-express

On Node 12 and up, this module can be loaded directly with import or require. On Node versions below 12, require or the esm-loader can be used.

Deno and Modern Browsers

You can load the EcmaScript module from various content delivery networks:

Usage Example

// index.js

const {dispatcher} = require ('fluture-express');
const app = require ('express') ();
const dispatch = dispatcher ('./actions');

app.use (dispatch ('welcome'));
app.listen (3000);
// actions/welcome.js

const {Json} = require ('fluture-express');
const Future = require ('fluture');

module.exports = locals => req => Future.go (function* () {
  const user = yield locals.database.find ('sessions', locals.session.id);
  return withStatus (418) (Json ({welcome: user.name}));
});

For a more in-depth example, see the example directory.

Documentation

Pseudo types

Req

The Express Request object.

Res a

The Express Response object with a locals property of type a.

The Response type

Fluture-Express mutates the response object for you, based on a specification of what the response should be. This specification is captured by the Response sum-type.

Response :: Type

The Response sum type encoded with daggy. You probably don't need to use this directly.

data Response a b = Respond (Array Head) (Body a)
                  | Next b

Head :: Type

The Head sum type encoded with daggy. You probably don't need to use this directly.

data Head = Status Number
          | Type String
          | Location String
          | Links (StrMap String)
          | Cookie String String Object
          | ClearCookie String Object
          | HeaderPart String String
          | Header String String

Body :: Type

The Body sum type encoded with daggy. You probably don't need to use this directly.

data Body a = None
            | Send Any
            | Json JsonValue
            | Stream (Future a Readable)
            | Render String Object

Stream -⁠> Future a Readable -⁠> Response a b

Creates a streamed response given a mime type and a Future that produces a Readable Stream when consumed. The Future is expected to produce a new Stream every time it's consumed, or if it can't, reject with a value that your Express error handler can handle.

Uses a Content-Type of application/octet-stream unless overridden by withType, withHeader, or withoutHeader.

Text :: String -⁠> Response a b

Indicates a textual response.

Uses a Content-Type of text/plain unless overridden by withType, withHeader, or withoutHeader.

Json :: JsonValue -⁠> Response a b

Indicates a JSON response.

Uses a Content-Type of application/json unless overridden by withType, withHeader.

Render :: String -⁠> Object -⁠> Response a b

Indicates a response to be rendered using a template. The first argument is the path to the template file, and the second is the data to inject into the template. This uses Express' render method under the hood, so you can configure it globally with app.set ('view engine', engine) and app.set ('views', path).

Redirect :: String -⁠> Response a b

Indicates a redirection. The first argument will be the response status code, and the second will be the value of the Location header.

Unless overridden by withStatus, the status code will be set to 301 (Moved Permanently).

Empty :: Response a b

Indicates an empty response. The response status will be set to 204, and no response body or Content-Type header will be sent.

Next :: b -⁠> Response a b

Indicates that this middleware does not form a response. The supplied value will be assigned to res.locals and the next middleware will be called.

withStatus :: Number -⁠> Response a b -⁠> Response a b

Configure the status code by setting up a call to res.status.

withType :: String -⁠> Response a b -⁠> Response a b

Configure the Content-Type by setting up a call to res.type.

withLocation :: String -⁠> Response a b -⁠> Response a b

Configure the Location header by setting up a call to res.location.

Configure the Link header by setting up a call to res.links.

withCookie :: CookieOptions -⁠> String -⁠> String -⁠> Response a b -⁠> Response a b

Configure the Set-Cookie header by setting up a call to res.cookie.

withClearCookie :: CookieOptions -⁠> String -⁠> Response a b -⁠> Response a b

Configure the Set-Cookie header by setting up a call to res.clearCookie.

withHeaderPart :: String -⁠> String -⁠> Response a b -⁠> Response a b

Append to a header by setting up a call to res.append.

withHeader :: String -⁠> String -⁠> Response a b -⁠> Response a b

Configure a header by setting up a call to res.set.

withoutHeader :: String -⁠> Response a b -⁠> Response a b

Removes a header from the Response. Also removes headers that would be set by functions like withType. For example:

> withoutHeader ('Content-Type') (withType ('json') (Empty))
Empty

Middleware creation utilities

middleware :: (b -⁠> Req -⁠> Future a (Response a c)) -⁠> (Req, Res b, (a -⁠> Undefined)) -⁠> Undefined

Converts an action to an Express middleware.

Takes a function that returns a Future of a Response, and returns an Express middleware that uses the returned structure to make the appropriate mutations to the res.

If the Future rejects, the rejection reason is passed into next for further error handling with Express.

dispatcher :: String -⁠> String -⁠> (Req, Res a, (Any -⁠> Undefined)) -⁠> Promise Undefined

Creates middleware that uses the export from the given file in the given directory as an "action".

It takes the file in two steps for convenience. You are encouraged to use the first parameter to set up a sub-directory where all your actions live.

The exported value should be a function of the same signature as given to middleware.

Downloads/wk

5

GitHub Stars

29

LAST COMMIT

2yrs ago

MAINTAINERS

3

CONTRIBUTORS

8

OPEN ISSUES

1

OPEN PRs

0
VersionTagPublished
6.0.1
latest
2yrs ago
No tutorials found
Add a tutorial
No dependencies found

Rate & Review

100
No reviews found
Be the first to rate