-Example
import { escapeHTML } from '@frontmeans/httongue';
import { httpListener, Rendering } from '@hatsy/hatsy';
import { dispatchByName, Routing } from '@hatsy/router';
import { createServer } from 'http';
const server = createServer(
httpListener(
Routing.and(Rendering).for(
dispatchByName({
hello({
route: {
url: { searchParams },
},
renderHtml,
}) {
renderHtml(
`<!DOCTYPE html>
<html lang="en">
<body>Hello, ${escapeHTML(searchParams.get('name') || 'World')}!</body>
</html>
`,
);
},
}),
),
),
);
server.listen(8080);
+Example
import { escapeHTML } from 'httongue';
import { httpListener, Rendering } from '@hatsy/hatsy';
import { dispatchByName, Routing } from '@hatsy/router';
import { createServer } from 'http';
const server = createServer(
httpListener(
Routing.and(Rendering).for(
dispatchByName({
hello({
route: {
url: { searchParams },
},
renderHtml,
}) {
renderHtml(
`<!DOCTYPE html>
<html lang="en">
<body>Hello, ${escapeHTML(searchParams.get('name') || 'World')}!</body>
</html>
`,
);
},
}),
),
),
);
server.listen(8080);
The server above responds with Hello, your-name-here! HTML at http://localhost:8080/hello?name=your-name-here
Goals
Hatsy is developed with the following goals in mind:
@@ -55,19 +55,19 @@ Hatsy
HTTP listener
httpListener([config,] handler) function creates a Node.js HTTP listener. It accepts an optional configuration and
a RequestHandler to process HTTP requests by.
HTTP processing configuration has the following options:
+HTTP processing configuration has the following options:
defaultHandler- A request handler to call if other handlers did not respond.Issues 404 (Not Found) error by default.
-errorHandler- A request handler to call when error occurred.By default, handles HttpError with corresponding status code and renders error page (either HTML or JSON).
+By default, handles HttpError with corresponding status code and renders error page (either HTML or JSON).
logError- Whether to log HTTP processing error.trueby default.
-handleBy- Creates actual HTTP request handler.This can be used e.g. to set up additional request processing capabilities, such as Logging.
+This can be used e.g. to set up additional request processing capabilities, such as Logging.
Request Handlers
Everything in Hatsy is implemented as a request handler, which is a function accepting a RequestContext as its only @@ -122,10 +122,10 @@
Hatsy
Dispatchers
Dispatchers are handlers that delegate processing to other handlers depending on request.
The following dispatcher implemented:
-
-
- dispatchByAccepted dispatches accordingly to content negotiation based on Accept request header. -
- dispatchByLanguage dispatches accordingly to content negotiation based on Accept-Language request header. -
- dispatchByMethod dispatches accordingly to HTTP request method. -
- dispatchError dispatches request processing error. +
- dispatchByAccepted dispatches accordingly to content negotiation based on Accept request header. +
- dispatchByLanguage dispatches accordingly to content negotiation based on Accept-Language request header. +
- dispatchByMethod dispatches accordingly to HTTP request method. +
- dispatchError dispatches request processing error.
Middleware
Connect-style middleware can be utilized by middleware function.
Hierarchy
Indexable
+
@@ -57,7 +57,7 @@ Optional
Optional
Starts to handle incoming requests by the given request handler.
@@ -163,7 +163,7 @@Returns